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
This endpoint is part of the V0 (beta) API. #18782
Comments
|
Thanks for the issue, we will take it into consideration! Our team of engineers is busy working on many types of features, please give us time to get back to you. Feature requests that require more discussion may be closed. Read more about our feature request process on forem.dev. To our amazing contributors: issues labeled To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @forem-team. The OSS Community Manager or the engineers on OSS rotation will follow up. For full info on how to contribute, please check out our contributors guide. |
Hi @szabgab, you're not doing anything wrong. That warning is a message we're using to notify everyone currently using the V0 API that a new version (V1) is available and we encourage you upgrade since we'll get rid of V0 sometime in the near future. Documentation isn't fully available under V1 but all of V0 endpoints are available in V1 without any major differences so you can reference either of them in the mean time. You can start using V1 exactly as you did before by passing in an I'm closing this issue for now, but feel free to reopen or create a new one if you find any issues with this. |
|
Thanks for the reply. Are you saying that my code used the V1 correctly? |
Not really. It's currently using V0 (the default). If you send the Accept header as I mentioned above it would start using V1 (explicitly requesting that version) and you'll stop receiving the warning header in the response. You'll likely see no difference in the result though since V1 includes all of the V0 endpoints, so in a way it would indeed use V1 correctly. |
|
I am getting back to this issue partially as only now I noticed your reply and partially because I still see the Warning 299 - This endpoint is part of the V0 (beta) API. To start using the V1 endpoints add the so I assume I am still not setting the header correctly. I tried to verify what my code sets so I changed the code a bit: This is the response I got: httpbin sees both the Accept header and the Api-Key header so I assume the dev.to API also sees it. |
|
ps. I don't see where could I reopen this issue. |
Using the following Python code:
I get:
As far as I can tell I've correctly set the header but this response still tells me I use V0 and tells me what to do. (That I've done)
If I was to fetch the response using
res.json()it seems the data is there, but I don't understand the warning.Am I doing something wrong or is this a bug?
The text was updated successfully, but these errors were encountered: