JSON Schema Parsing - Using $ref and $defs Prevents Titles + Description In UX/UI ( Still Validated ) #8689
Description
Severity
P4 - Low (Cosmetic/minor inconvenience)
Describe the Bug with repro steps
Potential Alternate Title: Complex JSON Schema Parsing Not Resolving In UX/UI
This is, potentially just a lack of functionality, but if so, I think perhaps it should be documented, maybe?
This occurs in request triggers and Parse JSON actions (or anywhere else one can utilise the functionality), I believe.
Basically, when using definitions in a schema via the JSON Schema accepted keyword of "$defs" these are not made available to the UX/UI interface as designed when providing things like a Title or Description either in the object with the "$ref" or in the definition itself.
I am aware that once you use a reference other keys are ignored, but nothing other than validation is even passed upstream from the definition.
This means that one cannot build gracefully for a client, or ones self, functionality that they can understand for future developments later in the same workflow.
My screenshots are from Power Automate, but I've experienced this frequently in Logic Apps, too.
This is agnostic of Windows or Linux OS usage, I do use Firefox, though.
What type of Logic App Is this happening in?
Consumption (Portal)
Are you experiencing a regression?
No response
Which operating system are you using?
Windows
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
Screenshots or Videos
Environment
- Browser: Firefox 141+
Additional context
Additionally, I have also tried 'definitions' in place of '$defs' with the same results.
Oh, and if you're thinking of changing to the alternative title, I'd add that referencing complex schemas yields similar UX/UI ignorance and is a shame, because we could really utilise it.