Update LB version to LB3

[nabdelgadir]

Description

Update LoopBack version from LoopBack 2 to LoopBack 3.

Related issues

• connect to Upgrade workspace from LB2 to LB3 #498

Checklist

• New tests added or existing tests modified to cover all changes
• Code conforms with the style guide

[bajtos]

@nabdelgadir The code base in loopback-workspace is ancient and some files (e.g. server/server.js) have not been updated to match the changes in project layout we made since early 1.x days 😞

Anyhow, here are the lines where to start learning about workspace internals:

loopback-workspace/server/server.js

Lines 35 to 38 in f95230a

	boot(app, __dirname);
	// file persistence
	require('./connector');

What is happening here: we are modifying memory connector in such way that queries are loading data from project files and updates are modifying project files. The implementation details shared by all models are in server/connector.js. Then there are entity methods Entity.allFromCache & Entity.saveToFs dealing with writing data to the filesystem, and ConfigFile.findFacetFiles, Facet.loadIntoCache etc. dealing with reading data from the filesystem.

I think the code inside individual model classes (Entity subclasses) should not need any changes to work in LoopBack 3.x. The code inside server/connector.js may need small tweaks to make it work with 3.x version of the memory connector, although it's also possible no changes will be needed.

[bajtos]

ok, the changes made so far looks good to me.

Now we need to find out why the tests are failing.

 1) ComponentConfig "before each" hook: givenBasicWorkspace for "should read data from "component-config.json"":
     Error: Cannot call WorkspaceEntity.destroyAll(). The destroyAll method has not been setup. The PersistedModel has not been correctly attached to a DataSource!

[nabdelgadir]

@slnode test please

[b-admike]

Nice work 👍

[bajtos]

I see the downstream builds for generator-loopback are still failing. While I think those test failure should not be related to this pull request, we cannot be really sure.

Let's fix generator-loopback first please. Then trigger a new build and see if all is good.

I opened a pull request to fix generator-loopback tests, see strongloop/generator-loopback#399 Once it's approved & merged, we should back-port it to 5.x branch of generator-loopback too.

cc @jannyHou

[bajtos]

@slnode test please

[bajtos]

@nabdelgadir all CI checks are green now, yay! 🎉