You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The frontend will be on 4.4 once we deploy the Angular upgrade. We should get backend and scripts on the same version. I took a quick pass at this, but the backend had a lot of type errors to resolve. Thus, I'm opening an issue for prioritization.
Everything compiles to JavaScript, so different TypeScript versions won't usually cause any issues running the application. However, shared bedes-common code will have to take care not to use TypeScript 4.x features, or the backend code won't compile. We'd notice this quickly, so not a major issue.
But making this change will also improve code quality and reduce future bugs, so it has benefits beyond reducing technical debt.
I personally think we should prioritize it, since it's related to the Angular upgrade in my mind.
The text was updated successfully, but these errors were encountered:
The frontend will be on 4.4 once we deploy the Angular upgrade. We should get backend and scripts on the same version. I took a quick pass at this, but the backend had a lot of type errors to resolve. Thus, I'm opening an issue for prioritization.
Everything compiles to JavaScript, so different TypeScript versions won't usually cause any issues running the application. However, shared
bedes-common
code will have to take care not to use TypeScript 4.x features, or the backend code won't compile. We'd notice this quickly, so not a major issue.But making this change will also improve code quality and reduce future bugs, so it has benefits beyond reducing technical debt.
I personally think we should prioritize it, since it's related to the Angular upgrade in my mind.
The text was updated successfully, but these errors were encountered: