-
Notifications
You must be signed in to change notification settings - Fork 1.5k
fix(core): Propagate field descriptions to generated Filter/Sort parameters #5065
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
grolmus
wants to merge
2
commits into
vendurehq:master
Choose a base branch
from
grolmus:mgrolmus/oss-659-propagate-graphql-field-descriptions-to-auto-generated
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+30
−0
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The production change is correct — I reverted both
description:lines locally and confirmed this test genuinely fails without them. Two things on the test itself.Use
printTypeagainst exact SDL, like every other test in this file. All 350 lines above assert viaprintType(...)+removeLeadingWhitespace(...); this one reaches intogetFields().name.descriptionbehindas any.printTyperenders the descriptions as docstrings, so a single comparison per generated type asserts both fields, both types, and that_and/_orcarry no docstring — in the form the rest of the suite uses, with noas any.It also drops
expect(..._and.description).toBeUndefined(), which pins an implementation detail: graphql-js orstitchSchemasnormalising an absent description tonullwould fail that assertion for reasons unrelated to the behaviour. WithprintTypethe question doesn't arise — either a docstring prints or it doesn't. The// synthetic fields ... remain undescribedcomment goes away with it.Cover the pre-existing-input merge path.
createSortParameter/createFilterParameterfold in fields from a hand-written{Type}SortParameter/{Type}FilterParameterwhen one exists (generate-list-options.ts:126-128,:167-169), and Vendure ships several —OrderFilterParameter,OrderSortParameter,ProductFilterParameter. Those fields flow through the same newfield.descriptionline, so documented hand-written SDL fields start emitting descriptions too. Currently untested. Second test below covers it (note the merged fields print before the source-type fields — that's the existing merge order, asserted as-is).Verified locally:
Tests 9 passed (9)description:lines deleted fromgenerate-list-options.ts):Tests 2 failed | 7 passed— both new tests fail