Skip to content
This repository has been archived by the owner on Mar 14, 2022. It is now read-only.

handling URI, UUID, other string formats from json-schema #145

Open
cmharlow opened this issue Jan 31, 2018 · 3 comments
Open

handling URI, UUID, other string formats from json-schema #145

cmharlow opened this issue Jan 31, 2018 · 3 comments
Labels
analysis next
Milestone
TACO API & Code

Comments

@cmharlow
Copy link
Contributor

No description provided.

@cmharlow cmharlow added the question Further information is requested label Jan 31, 2018
@cmharlow cmharlow added this to the TACO API & Code milestone Jan 31, 2018
@aaron-collier
Copy link
Contributor

Blocked by DRUID integration

@jcoyne jcoyne added the blocked label Feb 8, 2018
@cmharlow cmharlow mentioned this issue Feb 9, 2018
Closed
@cmharlow cmharlow added backlog and removed next labels Feb 23, 2018
@cmharlow cmharlow added next and removed backlog labels Mar 13, 2018
@cmharlow
Copy link
Contributor Author

No longer dependent on Swagger, but still can check string format using JSON MAP or other (confirm or deny this)

@cmharlow cmharlow removed the blocked label Apr 11, 2018
@cmharlow
Copy link
Contributor Author

can we use specific string format validation within json-schema (i.e. format: UUID). There is a particular go library we had been using with swagger to add string format validation (based of regex or known forms like UUID, URI, email, etc.).

@cmharlow cmharlow changed the title handling URI, UUID, other string formats from Swagger handling URI, UUID, other string formats from json-schema Apr 11, 2018
@cmharlow cmharlow added analysis and removed question Further information is requested labels May 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
analysis next
Projects
None yet
Milestone
TACO API & Code
Development

No branches or pull requests
3 participants
@jcoyne @aaron-collier @cmharlow