beenotung's recent activity
-
Comment on Just like Phoenix LiveView but in Typescript in ~comp
-
Just like Phoenix LiveView but in Typescript
@beenotung: Like the concept of SSR reactive web but not ready to use dynamic type Elixir for building webapp? TS LiveView get you covered 🤠https://t.co/Enrprt6G2N https://t.co/elOC0N2vXd https://t.co/W9pdg1FAAr
3 votes -
Comment on TSLint will be deprecated by the end of 2020 in favor of ESLint in ~comp
beenotung eslint offer more checking but some (if not most) or their rules cannot be autofix by the --fix flageslint offer more checking but some (if not most) or their rules cannot be autofix by the
--fix
flag -
Durov: Recent events showed once again that all WhatsApp users are at risk
8 votes -
Comment on TSLint will be deprecated by the end of 2020 in favor of ESLint in ~comp
beenotung tslint is deprecated and stopped accepting PRs (except security fixes). People behind suggest to switch to eslint. There is a tool tslint-to-eslint-config that try to help on the migration but...tslint is deprecated and stopped accepting PRs (except security fixes).
People behind suggest to switch to eslint.There is a tool
tslint-to-eslint-config
that try to help on the migration but seems some edges. For example indentation on generic type is not behaving as expected. The fundamental issue comes from the limitation in eslint.Currently typescript+eslint works by converting typescript AST to javascript AST, then pass to eslint for linting and auto fixing. However some rules in tslint are hard / impossible to be implemented by eslint because the AST used by eslint does not have the concept of 'typing'.
My personal view is to stay with tslint for typescript for now. eslint maybe used for javascript, but the UX is very poor when using eslint for typescript (at least in my current setting)
-
TSLint will be deprecated by the end of 2020 in favor of ESLint
7 votes
Like the concept of SSR reactive web but not ready to use dynamic type Elixir for building webapp?
TS LiveView get you covered ðŸ¤