I agree that it might be some deeper combination of my environment/settings. I just know that when I changed the layout of the component, my autocompletion started working beautifully again. Also, I didn't bother outlining in this brief article, but I've never had this problem with WebStorm and class-based components. Just the function-based ones.
As for TS, I'm on record now as being not-a-fan. But I'll readily admit that one of the cooler benefits of TS is that is makes your autocompletion sing - in pretty much any modern IDE that you choose.
I dabbled with TypeScript since 2014 and wasn’t a fan until I had to use it in a new job this year. There’s a bit of extra setup work and it takes some getting used to, but it’s completely worth it. It has an amazing type system that fits so well with the way JavaScript is used in the real world.
I would quibble over the idea that the "type system fits so well with the way JavaScript is used in the real world" (dev.to/bytebodger/key-headaches-in...), but I understand your point. 😉
I would argue that the reason to use typescript is for the auto completion benefits--which is a non trivial, super awesome benefit. And I guess I'm also including errors like "some _____ method doesn't exist on null" under the umbrella of auto-completion.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I agree that it might be some deeper combination of my environment/settings. I just know that when I changed the layout of the component, my autocompletion started working beautifully again. Also, I didn't bother outlining in this brief article, but I've never had this problem with WebStorm and class-based components. Just the function-based ones.
As for TS, I'm on record now as being not-a-fan. But I'll readily admit that one of the cooler benefits of TS is that is makes your autocompletion sing - in pretty much any modern IDE that you choose.
I dabbled with TypeScript since 2014 and wasn’t a fan until I had to use it in a new job this year. There’s a bit of extra setup work and it takes some getting used to, but it’s completely worth it. It has an amazing type system that fits so well with the way JavaScript is used in the real world.
I would quibble over the idea that the "type system fits so well with the way JavaScript is used in the real world" (dev.to/bytebodger/key-headaches-in...), but I understand your point. 😉
I would argue that the reason to use typescript is for the auto completion benefits--which is a non trivial, super awesome benefit. And I guess I'm also including errors like "some _____ method doesn't exist on
null" under the umbrella of auto-completion.