Display Conditional in Object Template #60
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.
A boolean mandatory: true or false is being used for displaying those attributes that are required when creating/updating an object
reading the RFC https://datatracker.ietf.org/doc/html/rfc2622 makes sense to me. Mandatory: true will be when we know that the attribute is required. Mandatory: false will be when the attribute is optional or conditional.
If we decide to change this, we should replicate the business logic when conditional (just to know if we should display the attribute or not as we do with mandatory - to know if that conditional is mandatory or not).
I don't think this is needed because the user could always add the "conditional" attribute if needed, when errors are thrown from backend.
We just need to make sure that the Condition is display in the object template, so the user can know before hand which is a conditional attribute. For that, it is enough just adding the whois dependency because the templates are being taken from whois dependency.