-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[CLA Approved] feat: AMD -> ES6 #7029
Conversation
Random tidbit but there seems to be some odd TS issue happening (there is a partial block by microsoft/TypeScript#55172), so I'll need to switch some functions into anonymous lambdas in the meantime. |
Current Playwright Test Results Summary✅ 166 Passing - Run may still be in progress, this comment will be updated as current testing workflow or job completes... (Last updated on 12/27/2023 06:56:30pm UTC)
|
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
Tabs View Renders tabbed elements
Retry 1 • Initial Attempt |
15.79% (6)6 / 38 runsfailed over last 7 days |
18.42% (7)7 / 38 runsflaked over last 7 days |
📄 performance/tabs.e2e.spec.js • 1 Flake
Test Case Results
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
Tabs View Renders tabbed elements nicely
Retry 1 • Initial Attempt |
6.90% (2)2 / 29 runsfailed over last 7 days |
3.45% (1)1 / 29 runflaked over last 7 days |
📄 functional/planning/timelist.e2e.spec.js • 1 Flake
Test Case Results
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
Time List Create a Time List, add a single Plan to it and verify all the activities are displayed with no milliseconds
Retry 1 • Initial Attempt |
0% (0)0 / 40 runsfailed over last 7 days |
67.50% (27)27 / 40 runsflaked over last 7 days |
scarily small - can see why this e2e coverage issue is high priority
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #7029 +/- ##
==========================================
- Coverage 56.02% 55.25% -0.78%
==========================================
Files 658 656 -2
Lines 26361 26617 +256
Branches 2546 2546
==========================================
- Hits 14769 14707 -62
- Misses 10893 11207 +314
- Partials 699 703 +4
*This pull request uses carry forward flags. Click here to find out more.
... and 6 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Odd - that one failing playwright test seems to be very flaky. I ran it locally, and it failed the first time, and was successful the second time. Maybe it's a timing issue? |
Hi @LeoDog896! Thanks for contributing to Open MCT! If you haven't already, please complete and submit a Contributor License Agreement (CLA). This is required before we can approve/merge your code.
Yep, that test is a current known flake, so likely not due to these changes.
I think that's a good idea. This will take a while to review, and it's probably best to take care of large changes like this in manageable chunks. While we're waiting for your CLA to go through, please let us know if you have any questions or if we can assist in any way. Thanks again for this work! |
Hi @LeoDog896 , Thanks for your patience. We're still waiting to hear back about your CLA. I'll follow up with the folks in charge of that to see if we can get a status. In the meantime, there have been quite a few changes since this PR was opened. Could you give a shot at resolving the resulting conflicts and let us know if you run into any issues? |
Sure! There shouldn't bee too many issues with merging; I'll resolve it in a bit. |
@LeoDog896 At long last, I've received a follow-up about your CLA being approved! I'll give a shot at bringing this PR up to speed as it's been sitting here for a while. Really appreciate your patience on this one. |
Alright, thanks! @ozyx, if you're not able to do it, then let me know - I completely forgot after saying my previous comment 😅 |
I'm not sure about the |
Yep, looks like the scanner is catching some more stuff now that we're using ES6. Awesome! |
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.
Really nice work! I've left a few suggestions, but this looks great overall. The tests are passing too! One thing I'd like to test is whether or not this changes how openmct
is used as a dependency. I suspect it should remain very much the same, but I'd like to verify that before we go ahead with this.
Testing against our testing environment with openmct as a dependency and have had no issues at all. Fantastic |
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.
Couple additional suggestions
Co-authored-by: Jesse Mazzella <[email protected]>
Co-authored-by: Jesse Mazzella <[email protected]>
Co-authored-by: Jesse Mazzella <[email protected]>
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.
This is looking great-- super excited to get this merged. Just one minor configuration fix
👍, anything else? |
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.
LGTM
Fixes #6975, finishing a step for switching to an alternative ES6-only bundler like Vite.
(This is currently drafted as not all tests pass - there was weird ES6/AMD conversion hacks going on in the codebase).
This isn't a full refactor to ES6 classes and ESMified code. I've converted a few to classes when the files were small or when necessary (e.g. with the main MCT class), but I've tried to avoid many refactors and only focus on AMD -> ES6 conversion. If this PR is accepted, I'll probably lead up with a second PR to finish cleanup of the rest of the folder.