Consistent file naming style

[bajtos]

In a slack-chat vote, we agreed to follow Angular's file naming convention in our project:

src/decorators/authenticate.decorator.ts

Now we need to clean up the code in loopback-next, loopback-next-hello-world, loopback-next-extension-starter (and possibly other repositories) to follow this new style.

Tasks

• Document the file naming style in our docs - either here on wiki, or preferably somewhere inside http://loopback.io/doc/en/contrib/code-contrib.html
• Decide on what convention to use for test file names - see the discussion here and here. Capture the convention in the docs.
• Update templates used by CLI to scaffold new projects, controllers, etc.
• Update loopback-next files to follow this convention
• Update other projects to follow this convention
  • https://github.com/strongloop/loopback-next/tree/master/packages/example-hello-world
  • https://github.com/strongloop/loopback4-extension-starter (deprecated)
  • https://github.com/strongloop/loopback4-example-microservices
  • https://github.com/strongloop/loopback-next/tree/master/packages/example-getting-started
  • https://github.com/strongloop/loopback4-extension-grpc
  • https://github.com/strongloop/loopback4-extension-typeorm (deprecated)
  • https://github.com/strongloop/loopback4-extension-mqtt
  • https://github.com/strongloop/loopback4-extension-graphql
    • rename graphql-component.ts to graphql.component.ts
  • https://github.com/strongloop/loopback-next/tree/master/packages/example-log-extension
  • https://github.com/strongloop/loopback-next/tree/master/packages/example-rpc-server

Out of scope

• Automatic linter enforcing our file naming convention Automatic linter enforcing our file naming convention #833

[dhmlau]

UPDATES (03/12):
Update the original description with updated links as we've moved the repos around.

[dhmlau]

Document the file naming style in our docs - either here on wiki, or preferably somewhere inside http://loopback.io/doc/en/contrib/code-contrib.html

I'm thinking the naming convention also applicable to users who are just creating LB4 app, not only contributing code. I wonder if it's a better place to put in the official documentation. Somewhere under "Best Practices" might be good, but don't know if it fits given what we have in this section.
http://loopback.io/doc/en/lb4/Best-practices-with-Loopback-4.html

[dhmlau]

Following up the discussion from here regarding the test file naming convention, the proposal was to have the type of test as suffix, i.e.
.acceptance.ts, .integration.ts, .unit.ts instead of .test.ts.

Also, I assume the test files are categorized by type as well. i.e.
test/acceptance/file1.acceptance.ts
test/integration/filexx.integration.ts

@strongloop/lb-next-dev , thoughts?

[shimks]

+1 for your proposal
i'm assuming we're advocating users name their test files as such for their artifacts?: user.controller.integration.ts

[shimks]

Updating convention on loopback4-example-microservices is tracked by strongloop/loopback4-example-microservices#94

[shimks]

Closing since it's done