complex paths in library fields #350
Merged
Conversation
This file contains 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
Rahien
changed the base branch from
master
to
karel/lmb-809-library-of-fields
Base automatically changed from
karel/lmb-809-library-of-fields
to
karel/lmb-333-create-form-extensions-in-app
January 14, 2025 12:41
JonasVanHoof
approved these changes
Jan 21, 2025
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
Allow complex paths in library fields. Example: datum van overlijden
How to test
Add the the field to a form, e.g. the correct mistakes form of a mandataris. See that the generators do their work and that the field is added along the path persoon:heeftOverlijden / persoon:datum
Links to other PR's