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
Refactor msp to modules #3214
Refactor msp to modules #3214
Conversation
fc5e62b
to
2359280
Compare
GUI.log(i18n.getMessage('infoVersionOs', { operatingSystem: GUI.operating_system })); | ||
GUI.log(i18n.getMessage('infoVersionConfigurator', { configuratorVersion: CONFIGURATOR.getDisplayVersion() })); | ||
gui_log(i18n.getMessage('infoVersionOs', { operatingSystem: GUI.operating_system })); | ||
gui_log(i18n.getMessage('infoVersionConfigurator', { configuratorVersion: CONFIGURATOR.getDisplayVersion() })); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like more the old way of GUI.log
(use a class/object and call the method). This way is outdated/discouraged in modules world?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That thing was causing most of the circular dependencies.
It's not Java or C#, there it literally no need to use classes here. Classes only make sense of data is stateful, this log does literally nothing more than reach into dom and append message. There is no need for it to be in class.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GUI in general is used in soooo many places and needs splitting up. log
should be it's own module/logic. But that's refactor for future. Now just fixing obvious issues.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we just call it log? Does it need gui_ ? That way you're just removing 'GUI.' and it's a suitable compromise.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's the log that appears in the GUI, in the upper part. We have too the console log. It's good to differentiate them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Open for other naming. We also have logging
tab and as @McGiverGim have console.log
so its rather overloaded term.
usbDevices not defined while flashing. |
ce02e2d
to
4f5b5be
Compare
@haslinghuis Fixed |
191a67b
to
24582f7
Compare
@chmelevskij thanks, as far I could test everything seems to work Please fix Tried to work it out but imports get 404. So might be a rollup thing. |
Upon further testing found (vtx tab):
|
037806f
to
ee7721b
Compare
This comment has been minimized.
This comment has been minimized.
ee7721b
to
4360043
Compare
@haslinghuis I think I've fixed the |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Testing now :) Yes vtxDeviceStatus looks like to be solved now !!! 🎉 🥳 ❤️ We should merge this soon. |
Do you want to test this code? Here you have an automated build: |
Refactors all of the configurator files to use ESM modules.
This doesn't fix any circular dependencies, that will have to come as different PR to reduce amount of changes.