-
Notifications
You must be signed in to change notification settings - Fork 311
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
Remove use of page=
query param for DevTools embeddings
#7405
Comments
We do use the |
Ooh actually, looking closer I see we're using |
We have a couple docs on this, but I'm not sure if it's appropriate to post here. I'll send to you directly for now. |
There are probably two parts to this question... How long to leave code in the SDK to support old versions of IDE plugins, and how long to leave code in IDE plugins to support old versions of the SDK. It's possible the answer is different for each of these (in part because upgrading SDK is often a much bigger job than upgrading IDE plugins and IDE plugins may frequently need to be updated to handle changes in SDKs). For |
I don't think we've thought much about the first issue (how long to leave code in the SDK to support old plugins) because of what you mentioned, that we frequently tell users to update plugins if they're having a problem. |
There is a TODO in the DevTools codebase to stop using the
page
query parameter from IDEs.@helin24 can you confirm that we do not use this from IntelliJ? If we do not use this, this issue can be closed. If we do, we should migrate to use the path based routing, which has been the DevTools standard for a number of years now.
The text was updated successfully, but these errors were encountered: