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

Fail to create resource using view/title button #363

Closed
alexweininger opened this issue Aug 17, 2022 · 6 comments
Closed

Fail to create resource using view/title button #363

alexweininger opened this issue Aug 17, 2022 · 6 comments

Comments

@alexweininger
Copy link
Member

Currently reproduces on 1.71.0-insider, caused by microsoft/vscode#157803

Repro steps:

  1. Click "Create Resource" from the view/title.
  2. Select any option (Function App for example)
Screen.Recording.2022-08-17.at.4.16.32.PM.mov
@alexweininger
Copy link
Member Author

Release of the feature that causes this bug is being delayed until September microsoft/vscode#42903 (comment)

I don't think this feature will break any other commands, it only impacts commands that are invoked via a view/title button. Currently the only commands we have for view/title are Create Resource, and Refresh.

@alexweininger
Copy link
Member Author

So seems like the new way they implemented it no longer breaks the commands.

@nturinski
Copy link
Member

Yep, confirms that it seems fine for me too, but should probably investigate what's really getting passed back.

@nturinski nturinski added 🔎 investigate 🕵️ and removed 🐛bug Something isn't working labels Sep 15, 2022
@alexweininger
Copy link
Member Author

investigation update...

The callback is passed two arguments, 1. the focused tree item, and then 2. an array of the selected tree items.

The focused tree item argument does replace our subscription argument, however, since each node has access to the subscription, it works all the same. We will have to plan for this for v2.

This does change the UX slightly. For example, if the user has two subscriptions shown previously we'd prompt them to pick a subscription. However, if the user has a node focused, the subscription that node is under will be auto picked.

@nturinski
Copy link
Member

Thanks for investigating this. I guess we shouldn't close it necessarily since we should keep it in mind, but then it shouldn't cause any issues 👍?

@MicroFish91 MicroFish91 added this to the 0.6.0 milestone Jan 11, 2023
@alexweininger
Copy link
Member Author

Fixed by a PR a while ago...

@microsoft microsoft locked and limited conversation to collaborators Feb 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants