refactor: extract helpers resolving relation metadata into own files #3410
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #3387 (spike for Inclusion of related models), I found a need to access resolved relation metadata from other files than just the repository factory. At the same time, I'd like to keep resolved metadata internal and don't export it from
@loopback/repository
, at least for now.In this pull request, I am adding three new files (
belongs-to.helpers.ts
,has-many.helpers.ts
andhas-one.helpers.ts
) and moving code related to resolution of relational metadata into these new files.This pull request is a pure refactoring with no impact on our users.
Checklist
👉 Read and sign the CLA (Contributor License Agreement) 👈
npm test
passes on your machinepackages/cli
were updatedexamples/*
were updated👉 Check out how to submit a PR 👈