Repository navigation
Conversation
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.
Summary
Load JPA entity relationship rules for EclipseLink, Hibernate, and standalone Jakarta/Java Persistence projects without requiring Spring. A shared addendum loader normalizes provider names, deduplicates persistence context, and supplies it to both file analysis and architecture prompts, including incremental dispatch; Spring retains its existing rules plus the shared JPA guidance.
Linked issue(s)
Closes #602.
How I tested this
Eight focused tests check provider aliases, Spring/JPA deduplication, existing framework handling, and the actual helper CLI consuming a scan result. No LLM analysis of a Java application was run.
pnpm lintpnpm --filter @understand-anything/core test— 1,013 passingpnpm test— 794 passing, 12 skippedpnpm buildVersioning