Replies: 4 comments 1 reply
-
TypeScript was specially useful when the comments section used React+GraphQL, since we synced the types. Now that it doesn't use React, we could probably drop it? I'm not specially used to JS/TypeScript development, so don't take my word too seriously 😅 |
Beta Was this translation helpful? Give feedback.
-
I have nothing against TypeScript but I do thing we should simplify if we can and have a consistent set of technologies. This will help to reduce dependencies which is always good. |
Beta Was this translation helpful? Give feedback.
-
Agree with all that was said. Afaik Typescript is great for complex js applications, but the trend with Decidim seems to be towards the Stimulus approach - minimum js, server rendered views. But it's been a while since I've done any js dev myself :) there might be a strong case made for typescript + stimulus I'm not aware of. Seems like Stimulus does support TS for those that want to use it |
Beta Was this translation helpful? Give feedback.
-
I agree with the general sentiment also, that having Yet Another Technology to maintain / learn / support it's too much mental overhead. +1 to getting rid of dropping Typescript support |
Beta Was this translation helpful? Give feedback.
-
I'm taking care of migrating to Webpacker (see #7291) and once of my concerns (one of many 😅 ) is the support to Typescript. AFAIK it's only being used to:
I think it won't be very difficult to get rid of it in (1) and (2) will be replaced by a simple
import
callI'd love to hear from you any feedback, consideration I'm missing, opinion...
Beta Was this translation helpful? Give feedback.
All reactions