@thomasglopes I do remember that when 3.0 was released, there were several discussions/RFCs about removing the behaviour but they didn't went through - https://t.co/TGzt5IKPU1
I don't think the #vue community has fully realised that we went from "Why can't Vue have the nice things" to having all the nice things (and more) when referring to headless/accessible UI libraries.
What a time to be a @vuejs developer!
@renaudrwemalika@michaelaubry @azizfargo @dhh Shit, we’re only 2 or 3 replies down and you already forgot the original tweet context? No typing system can save you from that! Ah! Cheers!
@renaudrwemalika@michaelaubry @azizfargo @dhh If you’re writing tests for types, you are missing the point: write tests for what the user sees; what’s rendered. types are just yet another implementation detail (omg the blasphemy, burn the whitch 🔥 !)
@michaelaubry @azizfargo @dhh Yeah like a page crashes because of a missing type and you blame the language. Write a fucking test for fucks sake. Do your job.
@rgfest6@gvns0x Don’t forget to take your own board: renting prices there are outrageously absurd. If you don’t have one buy a foamie from decathlon, it’s still cheaper than renting.
Enjoy, it’s a super fun wave 🌊
@calebporzio It’s possible. Done a vue wrapper with all those functionalities for a project (range, two months display and shortcuts). Didn’t make it abstract enough to become a library though.
@05karayel05@MichaelThiessen@vuejs The concept of "compound components" is not tied to react, you can achieve the same pattern in vue land using provide/inject which is "our" context provider.
But here's a good place to be inspired (has both react and vue versions) https://t.co/AXvUbldiEp
@MichaelThiessen@vuejs So "it depends" on your app context and how your UI system was built: with composition in mind (compound) or configuration (props heavy).
Both are valid options, i've done and still do both :p but leaning more towards "compound" version lately.
Cheers✌ (3/3)
@MichaelThiessen@vuejs "It depends". When we look past the simplistic use case, configuration scales proportionally to the amount conditions or side-effects you need: transition events; confirmation dialogs; action fns vs router links; different props for types of menu item layout; etc...(1/3)
Finally watched the new #MatrixResurrections. It’s like taking the blue pill: the magic ends, you wake up the next day in your bed and believe this is why we can’t have nice things.