-
Notifications
You must be signed in to change notification settings - Fork 102
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.
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
add JSON content type in response header #57
Comments
Thanks @shreddd.
Here is a short summary. But let's open a new meta issue right after to keep that separate from adding the JSON content type to the response header. One plan would be to:
Of course this is open to suggestions. We can discuss more in the separate issue. |
Opened #58 to keep track of the nbresuse roadmap. This issue is now pinned to improve visibility: |
Marking this current issue as a "good first issue", as it would require adding the content type to the endpoint in: https://github.com/yuvipanda/nbresuse/blob/master/nbresuse/api.py |
OK - thanks - super helpful. I may have one of our summer interns help with this. |
For the JSON API (currently /metrics but /api/nbresuse moving forward), it might be useful to add a "application/json" content type response header (which may allow for slightly easier parsing in certain clients).
Also - is there a set of upcoming changes / plans for nbresuse wrt the prometheus vs. JSON endpoints; the support for the statusbar etc.?
Before we contribute additional changes, it might be good to know what the plan is, so that we can figure out how best to target changes. I'm piecing together activity from various issues, but it would be good to see what was finally agreed upon moving forward.
The text was updated successfully, but these errors were encountered: