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.

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

Link v4 api pages back to v3 and vice versa #4454

Closed
1 of 2 tasks
s-taube opened this issue Sep 13, 2024 · 4 comments
Closed
1 of 2 tasks

Link v4 api pages back to v3 and vice versa #4454

s-taube opened this issue Sep 13, 2024 · 4 comments

Comments

@s-taube
Copy link
Contributor

s-taube commented Sep 13, 2024

On v3 API pages, we want to let people know v4 is now available. And on v4 pages, we want to link people back to v3 in case they didn’t migrate yet.

  • Below the headings on each v4 api page add the line: “V4 of the API is now live! We encourage you to use the latest version. You can view information on previous versions of the API here.” and link to the changelog (https://www.courtlistener.com/help/api/rest/changes/). This change should be made at help/api/rest/v4, as well each individual api page like api/rest/v3#case-law-apis, etc.

  • Below the headings on the v3 changelog page, add the line, “These notes are for a version of the API that has been deprecated and will soon be disabled completely. Please use the latest version, as these notes are only maintained to help with migrations.” This is what's provided already on help/api/rest/v2 and help/api/rest/v1. Link "latest version" to https://www.courtlistener.com/help/api/rest/v4.

@s-taube
Copy link
Contributor Author

s-taube commented Sep 13, 2024

@mlissner I was about to add this to the PR for Alberto as you requested, but I think I can make these updates myself?

@mlissner
Copy link
Member

Yes! You certainly can, but I was thinking an alert like this one would be best:

image

Want to take a look at that HTML and see if you can replicate it?

@s-taube
Copy link
Contributor Author

s-taube commented Sep 17, 2024

I made the update to v4, and commented in #4235 that v3 needs to be updated. (I figured it makes more sense for one person to make all updates to api/rest/v3 at once, rather than having to work around my one random change.)

@s-taube s-taube closed this as completed by moving to Done in @s-taube Sep 17, 2024
@mlissner
Copy link
Member

Great! Exciting to get these launched.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants