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

[Feedback] How to show that extension needs configuration? #152

Open
hiaux0 opened this issue Mar 12, 2021 · 3 comments
Open

[Feedback] How to show that extension needs configuration? #152

hiaux0 opened this issue Mar 12, 2021 · 3 comments

Comments

@hiaux0
Copy link
Member

hiaux0 commented Mar 12, 2021

Background

For me, #151 triggered this question.

On one side, I want to show a new user, how to setup the extension.
image

On the other side, it might become annoying (insert scenario).

Notes

When I use other extension, I would always go to the Repo and look for instructions.
Though, I always thought how nice it would be, if I get some setup instructions.

Options

  • A welcome page might be the solution?
  • Status Bar
@hiaux0 hiaux0 pinned this issue Mar 12, 2021
@zewa666
Copy link
Member

zewa666 commented Mar 12, 2021

I like that one. Alternatively you could also make the link open a tab with a webview embedding the readme from the repo. Similar like gitlens has

@pkkummermo
Copy link
Contributor

I use VSCode on several projects, also ones where aurelia is not present. The extension follows VSCode and not only the workspace. Perhaps we could detect if aurelia is actually present (searching package.json) before we show error/warnings/start pages?

@hiaux0
Copy link
Member Author

hiaux0 commented Mar 17, 2021

Thanks for the proposals, which are

  1. Link should open in webview (cf. gitlens)
  2. Auto-detect Aurelia project

I started on 2.

Strategy:

  • Detect if any Aurelia-related files are open
    • Yes? -> Start component collection
    • No? -> Do nothing
      • And wait until Aurelia-related file is being opened -> Start component collection

@hiaux0 hiaux0 unpinned this issue May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants