Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

how to map APIs.json collection properties #4

Open
dret opened this issue Dec 10, 2019 · 1 comment
Open

how to map APIs.json collection properties #4

dret opened this issue Dec 10, 2019 · 1 comment
Assignees
@u1i

Comments

@dret
Copy link
Collaborator

dret commented Dec 10, 2019

https://etiketo.org/values/APIs.json/ has a list of which label value types to use for APIs.json properties. the last two are not really working as specified there, because they aren't just strings or sets of strings. how are we mapping those to etiketo? even if we cannot map them and ignore them we should say so, but maybe we can do better than that?
@dret dret assigned u1i Dec 10, 2019
@ioggstream
Copy link
Contributor

Q: my understanding is that apis.json was not widely adopted, eg see:

OAI/OpenAPI-Specification#1973 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@u1i u1i

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ioggstream @dret @u1i