Repository navigation
Conversation
aaqilniz
force-pushed
the
feat/relation-in-discovery
branch
3 times, most recently
from
October 4, 2025 14:24
3747874 to
d1bf2a5
Compare
relations: true
aaqilniz
marked this pull request as ready for review
October 4, 2025 14:32
aaqilniz
force-pushed
the
feat/relation-in-discovery
branch
from
October 25, 2025 03:31
d1bf2a5 to
b36f8e8
Compare
Coverage Report for CI Build 44127368436Warning Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes. Coverage increased (+0.2%) to 55.067%Details
Uncovered ChangesNo uncovered changes found. Coverage Regressions441 previously-covered lines in 32 files lost coverage.
Coverage Stats💛 - Coveralls |
aaqilniz
marked this pull request as draft
November 14, 2026 13:43
relations: truelb4 discover
lb4 discoverlb4 discover
aaqilniz
marked this pull request as ready for review
November 17, 2026 17:31
Signed-off-by: Muhammad Aaqil <aaqilcs102@gmail.com>
aaqilniz
force-pushed
the
feat/relation-in-discovery
branch
from
November 19, 2026 16:16
07e7dbc to
f68d346
Compare
aaqilniz
marked this pull request as draft
November 19, 2026 16:18
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Building upon PR#8461, which introduced model-level relation generation when discovering models with
relations: true, this pull request extends functionality to complete end-to-end relation discovery.While PR#8461 successfully decorates the model classes, introspected relations currently fail at runtime because repositories lack the required accessors and controllers lack the REST routing endpoints. This PR implements the complete synchronization required across all three tiers (belongsTo model decorators, repository factories/inclusion resolvers, and REST controller routes).
Support for inverse relations (hasOne, hasMany) will be introduced in a subsequent pull request once exported foreign key introspection is expanded.
Change
Model Property Transformation: Safely merges existing column properties into unified relation decorators without duplicating properties.
Repository Integration: Automatically generates repositories and injects Getter parameters, registers repository factories (createBelongsToAccessorFor), and adds inclusion resolvers to source repositories.
Controller Generation: Scaffolds relation-specific REST controller files with proper OpenAPI schema definitions (getModelSchemaRef) and routing paths.
Checklist
npm testpasses on your machinepackages/cliwere updatedexamples/*were updated👉 Check out how to submit a PR 👈