-
Notifications
You must be signed in to change notification settings - Fork 16
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
💡 [Feature]: Present solutions deployed per app catalog #215
Comments
Hi @Adam-it , Can you assign this to me please? |
Sure thing. |
Sure. Thank you :) |
Hi @Adam-it, The account signin is not working. |
how did you obtain cli-cjs version?
|
this error says that you are using esm version of js which is not supported in VS Code extensions. |
It works after cleanup. Thanks for looking into it. I will work on this issue soon; have a great summer. :) |
Hi @Saurabh7019 |
Hi @Adam-it , Thanks for checking in. Most of the features are done, except for the 'Move apps between app catalogs' part. Also, to improve the extension load times, I made changes in ActionTreeDataProvider so that apps and extensions are loaded only when the user expands the relevant tree view node (I can undo this if needed during review). Right now, it looks like this: I did most of the work during the summer vacation, but I am struggling to find time to wrap it up now. In hindsight, we should have broken this into multiple issues; it would have made things easier. I will try to work on "Move apps" feature early next week and raise a PR. |
wow looks really awesome 🤩 You Rock 🚀😍.
BTW awesome to see you are also using the CLI VS Code extension 😍 |
|
🎯 Aim of the feature
The aim of this issue is to show apps deployed to each app catalog (similar way like we now present tenant-wide extensions for tenant level app catalog)
Additionally, we could introduce the following features:
we should add an extension setting that will allow to hide this information in the UI
📷 Images (if possible) with expected result
🤔 Additional remarks or comments
parent issue: #15
The text was updated successfully, but these errors were encountered: