Echo JS 0.11.0

<~>

jaleksic comments

jaleksic 2128 days ago. link 1 point
I've been using this approach in a couple of projects now, and I must say it's a pleasure to work with and saves a lot of repetitive coding, and improves UX easily.

I've now rewritten it to use less code (thanks to the hooks API) and I added some examples and wrappers for popular UI libraries (semantic-ui-react, react-bootstrap, antd, plus Material UI example)
jaleksic 2139 days ago. link 1 point
I'll give this a test ride with the next prototype project! I wonder how it turns out in practice, and what kind of caveats await, but again, I really think it looks promising!
jaleksic 2142 days ago. link 1 point
Very promising concept, and the docs and examples are very good reads! Thumbs up!

I was surprised to see that targeting multiple classes happens with a query selector, as in: className="btn-primary.disabled".
I had expected className="btn-primary disabled" as it feels more natural. I imagine the implementation overhead for that feature would be worth it, but of course I don't know any details.
jaleksic 2204 days ago. link 1 point
Don't understand the downvote. I think this is a really well-written and knowledgeable article.
jaleksic 2310 days ago. link 1 point
Oh shoot, sorry for multiple comments, posted with flaky connection. Admins please feel free to remove.
jaleksic 2333 days ago. link 1 point
I used flowcheck in a project once, with flow checking even at runtime.
It's deprecated in favor of https://github.com/gcanti/babel-plugin-tcomb now. Still not the same as proptypes.

I've seen typescript react code recently where in addition to typescript interfaces, proptypes were used too. Not sure why that is. I understand that typescript gives you good integration with some editors or IDEs. Not sure why you'd need proptypes on top. But then again, I don't really know much about the topic. Maybe somebody will clarify things in this "thread".

Personally, I'm happy with the way proptypes work. I see it as lightweight assistance during December, not as something that guards me/my code against bugs or problems.
jaleksic 2391 days ago. link 2 points
A friend just told me I could have just used the nohoist feature of yarn workspaces to avoid hoisting mix-ups with Babel.
Well.. maybe this tool is still worth something to someone :)
[more]