Fix #560 - removed equality check between fieldKey and name in return condition of addFieldDepedency() to allow addition of the field itself as a dependency #561
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
This PR will close #560
Enable an user to add a field as its own dependency under displayLogic, so that a field display can change based on a value of the field itself.
Motivation and Context
In my project using CRM, I have a field which requires to adjust its display type based on a value of the field itself.
How To Test This
For any field, configure the field itself as a dependency such as follows as an example:
Types of changes
Final checklist