-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
feat: Add Floating button for admin page #3138
base: master
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
All contributors have signed the CLA ✍️ ✅ |
Hi! Thank you for taking the time to contribute. I can see you put a lot of work into this to match our existing APIs & internal patterns 👍 Regarding the feature itself, I will reference #1645 which is upcoming work in which we are refreshing the Admin UI generally. It is possible that this feature would fit into the new designs, so we'll revisit it at that point. |
Is there a place where i can track this ?
Thanks in advance😁 |
I have read the CLA Document and I hereby sign the CLA |
You can run |
Hi, thanks for the suggestion, i having issues where the admin-ui that i published can be download but can't import, showing error that the IDE can't find the admin-ui folder Using vscode and navigate to the node_modules/@my-org have no sign of the admin-ui (this is also the case for @vendure) but using cli and cd to that location still show that the admin-ui does exist Is there a config where the admin-ui package is hidden from the ide ? Edit: my admin-ui build looks difference from yours, when viewing your admin-ui, it's shows core,dashboard,etc folders, but mine require to cd in the package folder to view those folder Edit 2: i only build and publish admin-ui, admin-ui-plugin, ui-devkit |
Quality Gate passedIssues Measures |
Description
I added the ability to include floating action buttons in the admin UI. Admins/users can have quick access to actions on all pages, just on specific routes or based on the current user's permissions.
Usecase:
Breaking changes
No
Screenshots
Checklist
📌 Always:
👍 Most of the time:
I'm writing test cases and update README files and will commit them soon. Right now i'm looking for your feedback about this feature and should i improve it more