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
Currently the significant part of the frontend codebase is opted-out from TypeScript core features. It's done by using both implicit and explicit any, @ts-ignore, strict: false, lack of HTTP request/response typings or using less strict types while higher specificity is possible (e.g. using type string when only values a and b are possible).
There are several steps that can be performed to make the code more type-safe. That will enable us to reduce nb of bugs related to incorrect typings of data that is coming from the backend / incorrect payloads passed in requests as well as catch possible issues quicker (during development instead of after deployment), improve developer experience (intellisense) and improve readability.
The initiative includes the following issues:
Issues in both groups are sorted by the order they should be picked up. It is possible to work on both groups in parallel with just one exception - it would be great to have #3330 from Group A before starting to work on Group B
The content you are editing has changed. Please copy your edits and refresh the page.
Currently the significant part of the frontend codebase is opted-out from TypeScript core features. It's done by using both implicit and explicit
any
,@ts-ignore
,strict: false
, lack of HTTP request/response typings or using less strict types while higher specificity is possible (e.g. using typestring
when only valuesa
andb
are possible).There are several steps that can be performed to make the code more type-safe. That will enable us to reduce nb of bugs related to incorrect typings of data that is coming from the backend / incorrect payloads passed in requests as well as catch possible issues quicker (during development instead of after deployment), improve developer experience (intellisense) and improve readability.
The initiative includes the following issues:
Issues in both groups are sorted by the order they should be picked up. It is possible to work on both groups in parallel with just one exception - it would be great to have #3330 from Group A before starting to work on Group B
Backend
Frontend
any
#3329any
#3333Tasks
The text was updated successfully, but these errors were encountered: