-
Notifications
You must be signed in to change notification settings - Fork 107
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
1301 use wails for front end #1302
Conversation
51663af
to
e96876e
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1302 +/- ##
=======================================
Coverage 22.09% 22.09%
=======================================
Files 29 29
Lines 1715 1715
=======================================
Hits 379 379
Misses 1326 1326
Partials 10 10 ☔ View full report in Codecov by Sentry. |
1e9e62a
to
1112799
Compare
41cb264
to
7b18a9a
Compare
fc08020
to
85c4fe7
Compare
Current state:
In conclusion, Wails v3 will be a great product once ready. But for now, the alpha versions lacks of features and are still too unstable for MS, even for an alpha release. We might come back to Wails for MS once it is more stable So, Moving MS to Wails is in standby and this issue will be closed. |
Linux feedback on Wails discord: https://discord.com/channels/1042734330029547630/1199715431997517925/1199715431997517925 |
Please do not waste your time reviewing:
_test.go
files: Mainly changes due to linter update. Tests were not modified.web/massastation/wailsjs/
: Those are generated files from Wails.Delivery Quality Checklist
Breaking Changes in API:
Does this PR introduce breaking changes in the API?
Changelog:
Version Update Handling:
Have you ensured that the version update by user is handled correctly?
PR Dependency:
Does this PR depend on another PR?
Documentation: