Repository navigation
Change in proposed API handling? #3078
Replies: 2 comments 3 replies
|
I just modified end-to-end tests to test the first supported version and latest with different CLI arguments: https://github.com/s-h-a-d-o-w/dev-containers-oss/blob/7625386a65f69e277b126049e75882797cc259ee/tests/baseTest.ts#L97-L100 |
Maybe, it was a bug since unauthorized api shouldn't work.
Those users are devs so they should be fine, even thought sometime I wonder... (from the question I got asked on this project) I do think it was a bug for those versions since the workaround was always needed. Line 40 in be70704 I need to get a policy on how/when to add new api. I've got a request for that just few days ago (#3074). |
Uh oh!
There was an error while loading. Please reload this page.
I couldn't find anything recent related to proposed API handling in this project, so it might come from upstream but... the impact is strange.
Because we have all read about the workarounds with having to start with an argument or modifying
argv/product.jsonthat seem to have existed for years.Yet... v126 and v135 allow my devcontainer extension to run without such workarounds.
v140 suddenly doesn't any more.
Any insight on this and whether this can be fixed? Because obviously, making users mess around with config just to get an extension running when it previously wasn't necessary, isn't a great user experience.
All reactions