-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add support in the GUI for new output types #5
Comments
@peterjaap DB schema are still WIP and subject to change 🙃 |
Not WIP anymore - docs here https://github.com/AmpersandHQ/ampersand-magento2-upgrade-patch-helper/blob/master/docs/CHECKS_AVAILABLE.md :) |
Checks are listed in this file Queue consumers are always Db schema can be both |
Some work being done in https://github.com/elgentos/magento2-upgrade-gui/tree/info-notices |
Ok I've merged the work I've done into 1.3.1. Notable changes;
The INFO notices button doesn't do anything yet except show an alert box saying it's not implemented yet; Next step is to create an actual screen with the notices displayed. |
I hope that is related to this issue: I see Console prints:
|
Where do you see the db_schema.xml output? It shouldn't show up in the GUI anywhere at this point. Could you share a screenshot? |
Along with the other lines in the dropdown at the top... |
@amenk fixed in 1.3.4 |
@amenk amended in 1.3.5. I previously filtered out the "DB changed" WARN notices, but I re-added them and show a notice on the right hand side why no file is shown for "DB changed added" WARN notices;
|
Works well :-) |
The amazing @convenient added a few output types to the Ampersand tool (see commit);
Right now, this info is nowhere to be seen in the GUI, so we need to add it.
I'm terrible at UI, so maybe someone has an idea of where to show it. My thought would be to show an Info button on this page somewhere:
Maybe with an indicator of how many INFO notices there are. When clicking on it, you'll go to a screen that shows all the warnings?
Hint;
magento2-upgrade-gui/src/background.js
Line 163 in 26cfa80
The text was updated successfully, but these errors were encountered: