This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 645
"useApiV1": false
vs --api-version=2
#1876
Comments
It is a reasonable request The intended release plan of the delve V2 integration was to have this compatibility config flag during a couple of releases using V1 as the default, and then make the final switch to V2 |
If that's the case then it also fine, less config is better :) +1 for default V2 and removing the useApiV1 flag completly |
I was meaning to set v2 as default for a while now, but was waiting to have an update which didnt have any other debug related changes, so that if there were any issues I could narrow it down to the version change. Now is a good time, I'll make the change |
ramya-rao-a
added a commit
that referenced
this issue
Sep 10, 2018
ramya-rao-a
added a commit
that referenced
this issue
Oct 3, 2018
In the latest update to this extension (0.6.90), we use v2 by default. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
"useApiV1": false
works great but what if someday we have a V3Can we have a refactor that is consistent with the dlv cli flags
--api-version=2
as in"api-version":2
and the default is 1Thanks
The text was updated successfully, but these errors were encountered: