-
-
Notifications
You must be signed in to change notification settings - Fork 308
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
"Angular Upgrade: Incremental Approach (v13 → v19)" #379
base: master
Are you sure you want to change the base?
"Angular Upgrade: Incremental Approach (v13 → v19)" #379
Conversation
3c6a2d5
to
ed0c258
Compare
Thank you for your effort, @yashchauhan4579 🙌 🏆 (I'm no Angular expert so I'll refrain from reviewing, but from what I could tell, it looked all good : ) |
ed0c258
to
7f85983
Compare
…le Angular analytics
7f85983
to
3612bad
Compare
Thanks for the efforts @yashchauhan4579 ! Let me know if you run across any issues. I would be happy to guide you. |
@yashchauhan4579: I just want to clarify your thoughts of progress. Are you planning on upgrading all the steps until v19 in this PR? Or do you want to split it up in multiple PRs? Also, do you have a rough timeline? No pressure, what so ever. Main aim is coordinating any other changes. If you feel like a pause before reaching v19, please let us know and tag 0x41head. Then we can do the review of the progress, and close / merge this PR. (And enabling merging any other UI issues in between. : ) |
Thanks for the acknowledgment, @0x41head! I appreciate your support. I'll reach out if I run into any issues.👍🏻 |
Thanks for checking in, @vbakke! I’m currently progressing step by step with the upgrade to ensure stability at each stage. I’m also considering the approach of structuring it into multiple PRs if that helps streamline reviews and maintain better coordination. Before finalizing the strategy, I’d like to discuss this with @0x41head to align on the best course of action. I’ll assess the progress and confirm the next steps accordingly. Proper coordination is essential to facilitate seamless upgrades while accommodating other UI changes. Thanks again! |
Hi @vbakke, coming back to you with an update! I plan to complete the full upgrade to v19 in a single PR. I estimate it will take around 2-3 weeks to ensure stability and prevent regressions, if thereafter there is a need for stretch I would actively Inform. And If I run into any hurdles during the process, I'll consult with @Ox41head to ensure everything moves forward smoothly. I hope this aligns well with the ongoing processes! |
Angular Upgrade (Incremental v13 → v19)
Summary
This draft PR aims to upgrade the Angular version of DSOMM from v13 to v19 incrementally to ensure smooth transitions and minimize breaking changes.
Approach
Started with v13, upgrading step-by-step to v14, v15, v16, etc.
Addressed dependency changes and fixed compatibility issues.
Testing after each upgrade to ensure stability.
Current Progress
*Upgraded to v14
*Next: Upgrading to v15
Next Steps
*Continue incremental upgrades until v19.
*Fix potential issues and dependencies along the way.