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

Design Guidelines: HTTP Status Code type should be Integer, not String #58

Closed
bigludo7 opened this issue Feb 3, 2023 · 5 comments
Closed

Design Guidelines: HTTP Status Code type should be Integer, not String #58

bigludo7 opened this issue Feb 3, 2023 · 5 comments

Comments

@bigludo7
Copy link
Collaborator

bigludo7 commented Feb 3, 2023

Hi
We need to change again :)

See camaraproject/WorkingGroups#143

No hurry there for next API update we should align.
@PedroDiez
Copy link
Collaborator

hahaha, yes Ludovic.

Let's wait until the conclusion of that track, because as an integer, "pattern" concept does not apply but the use of:
minimum:
maximum:
probably would be the suitable one.
Think this is gonna be moved in Commonalities

@PedroDiez
Copy link
Collaborator

Let's keep this Issue Open.
Think can take still some time to have an alignment. Just to have track of it when considering this in a higher version

@PedroDiez
Copy link
Collaborator

Open thread in Commonalities: camaraproject/WorkingGroups#151

@PedroDiez
Copy link
Collaborator

Currently being addressed in camaraproject/WorkingGroups#162

Model is the one fllowed within WG, just will take out pattern from "status" as pattern applies for string fields

@PedroDiez PedroDiez mentioned this issue Mar 7, 2023
Merged
@PedroDiez
Copy link
Collaborator

Set to closed as covered in PRs: #60 and #64

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@PedroDiez @bigludo7