Import loopback-datasource-juggler using lerna import

[dhmlau]

Part of #890 epic

Monorepo layout proposed by @bajtos, inspired by loopback-next:

path	description	example
/packages/{name}	place for juggler and dependencies	packages/filters (formerly loopback-filters)
/connectors/{name}	directory for all connectors	connectors/base (formerly loopback-connector)
/examples	place for example applications	/examples/todo

Acceptance Criteria

• Create a new monorepo where we will develop juggler, connectors and dependencies [juggler-next for now, not so important]

• Enable the following permissions for the new GitHub repository:

  • Admin role for @strongloop/loopback-admins
  • Write access for @strongloop/loopback-maintainers
  • Read-only access for @strongloop/loopback-next

• Import the following packages/GitHub projects using lerna import to preserve git history:

  • loopback-datasource-juggler
  • loopback-filters
  • loopback-connector

• Rename package names, use names in @loopback scope (e.g. @loopback/filters). Discuss the names with the team first.

• Change the version number of all packages to 0.1.0.

• Set up Continuos Integration and Code Coverage. Use the same approach as we do in loopback-next (e.g. Travis CI + AppVeyor now, but we may switch to Azure Pipelines):

  • Linux (Node.js 8.x + 10.x)
  • MacOS (Node.js 8.x + 10.x)
  • Windows (Node.js 8.x + 10.x)
  • code coverage

• Start documentation for developers, explain monorepo layout and how to accomplish common tasks. See loopback-next's DEVELOPING.md for inspiration.

IMPORTANT Keep the amount of changes made in the actual code (juggler/filters/connector) as little as possible. Not allowed: changes in the way how packages work (functionality/behavior/API), how the code is structured or formatted.

Out of scope

• migration to TypeScript
• commit linter - Enable commit linter in juggler monorepo #1739
• code linters: prettier - see Switch to prettier formatting in juggler monorepo #1740; tslint/eslint - see Enable code linter in juggler monorepo #1741

Reference

See more detailed discussion in #890

[stale]

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

[stale]

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.