Name attribute missing from Schema interface
See original GitHub issueThe org.eclipse.microprofile.openapi.annotations.media.Schema
annotation defines a name
attribute for the purpose of naming the schema or property to which the annotation is attached. However, there is no such property on the org.eclipse.microprofile.openapi.models.media.Schema
interface to allow for programmatic retrieval or setting of the name attribute.
I was not able to find any previous issues or discussion as to why it would be missing in the interface. Is this an intended omission?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
XML Schema: Referenced attribute is missing - Stack Overflow
When validating the the following XML against the schema, the reference attributes of KeyB are marked as missing/undeclared unless prefixed ...
Read more >Known issues for application provisioning in Azure Active ...
Extensions to your schema can sometimes be missing from the source attribute dropdown in the UI. Go into the advanced settings of your ......
Read more >Unions and interfaces - Apollo GraphQL Docs
Unions and interfaces are abstract GraphQL types that enable a schema field to return one ... GraphQL type and returning the name of...
Read more >PutItem - Amazon DynamoDB - AWS Documentation
A map of attribute name/value pairs, one for each attribute. Only the primary key attributes are required; you can optionally provide other attribute...
Read more >Dynamically Add/Remove Attributes in Custom Transformer ...
The user interface will still display names of attributes that are dynamically removed even when they are not there. 'Missing' in FME terms, ......
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 FreeTop 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
Top GitHub Comments
After some further study of the API, it has become obvious that the name is not a part of the
Schema
interface because the name is held as the key in theMap.Entry
where theSchema
is the value.That is -
Becomes -
Map.Entry<String, Schema>
where the key is “foo” and the value is an instance of theSchema
interface.OK that’s probably fine for that use-case then.