[BUGFIX] subfields#1226
Merged
Merged
Conversation
field.name only prefixes parent_field name when it is not a relation
jasper-jager
approved these changes
May 4, 2026
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.
field.name gebruikt alleen de parent prefix als die parent geen relatie is. Dit zorgde ervoor dat als:
er een 500 error kwam omdat het ongeprefixte veld werd opgevraagd. In het specifieke geval van meetbouten ging dat fout omdat er een aantal velden met subvelden was met een volgnummer, terwijl meetbouten zelf dat veld niet hebben.
Heb geen zeer specifieke test ervoor geschreven, omdat het uitbreiden van de bestaande test al laat zien dat subvelden goed doorkomen.