refactor(core): export Constructor from @loopback/context

[virkt25]

Description

Enables it's use in extension / application development without a dependency on @loopback/context

Related issues

• build: Update @loopback deps to latest version strongloop-archive/loopback4-extension-starter#11 (comment)

Checklist

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

[bajtos]

Ideally, extensions should not depend on @loopback/core, but on @loopback/context only. Is it possible to achieve that?

If not, then I am ok with this change. It may be better to (re)export everything fomr @loopback/context in such case:

export * from '@loopback/context';

[virkt25]

It is most certainly possible to use @loopback/context. My reason was that we require inject from core and it seemed weird to me to require Constructor from context. (I was just trying to keep the developer experience simple). That said more I think about it, it’s probably better to keep this separate since I think only extension developers would be using this and not application developers.

[bajtos]

My reason was that we require inject from core and it seemed weird to me to require Constructor from context. (I was just trying to keep the developer experience simple).

Can we import both inject and Constructor from context then?

Not a big deal, I'll leave it up to you to make the final decision.

[virkt25]

Closing to avoid promoting re-exporting types not needed for Application Development. The currently re-exported functions are ok as they avoid requiring an Application Developer to import Context just to get started.

Best practice for extension developers will be to import them directly from @loopback/Context.