Support additionalItems in CommonModel
See original GitHub issueReason/Context
The CommonModel currently has no knowledge of additionalItems
that the array/tuple must also support. This should change in the same way as additionalProperties
are implemented.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
additionalItems does not support $ref · Issue #408 - GitHub
Describe the bug The additionalItems should support schema including $ref { "$schema": "http://json-schema.org/draft-07/schema", ...
Read more >DFHPI9702 E - IBM
DFHPI9702 E Unsupported JSON schema. A JSON schema "type" of "array" with an "additionalItems" keyword is only supported with value false.
Read more >Solved: vRO 8.5 failed to save workflow schema {{message}}...
I went in to modify that array and add a couple of additional items and when I do I get an error 400,...
Read more >MarkLogic from a Relational Perspective: Part 2
With MarkLogic, best practice is to maintain data as it was originally received/ingested, while enhancing and harmonizing as additional items.
Read more >Delivery Context Ontology .- Delivery Context Terms
Delivery Context - This class represents the set of characteristics that describes the context in which materials are exchanged between a service and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Lets not overcomplicate it as we have no use-case for
2019-09
as of yet. Once we do we can adapt for it 🙂🎉 This issue has been resolved in version 0.12.0 🎉
The release is available on:
Your semantic-release bot 📦🚀