Kierkegaard Turdhammar

Is there a SaaS product to solve nuance at scale?

@snyksec Curious how according to the package health checks here, Vue.js has no contributors (when it does) and no code of conduct (when it does) snyk.io/advisor/npm-pa…

@aboodman @bleikamp why i have to click to see that a page has no children

@bleikamp I love Notion, and as a software eng who cares a lot about ux I enjoy comparing notes with those who dislike it. It reminds me how wide experiences can be. What are your top gripes?

I feel like I'm going insane but Notion is not actually very good software How did they trick everyone?

@thomaspaulmann @raycastapp clipboard history 'information' showing 'copied' timestamp without needing to scroll. ideally above word/character count

Ok, you can change one thing in @raycastapp, what is it?

@TheTexasNative @tender_jay @__C0ldbrew__ @adammocklerr Sure, I guess you were just providing info, not making a point. But when your info is a government policy website it's not always easy to understand. Just clarifying that the source confirms no tariffs charged by Canada on imports from the US

@thedamon @tender_jay @__C0ldbrew__ @adammocklerr I just provided you with the literal list of all Canada/US tariffs.

This post from a Canadian Redditor hits hard:

@TheTexasNative @tender_jay @__C0ldbrew__ @adammocklerr you see the ''Appliciable preferential tariffs" column? Look for "UST" there (The United States-Canada Trade Agreement) to see the rate for the US (it's gonna say 'free', bc there isn't a tariff for the US)

@tender_jay @__C0ldbrew__ @adammocklerr List of all previous tariffs from 2024, none of these are the newer tariffs. cbsa-asfc.gc.ca/trade-commerce…

@calebporzio totally cool if it's just fun. but.. this doesn't look clean to me :D `[,` looks like it needs housekeeping!

@calebporzio what's the benefit over the much more readable `let second = array[1]` ?

btw, clean way to get the second element in an array if you've never seen this

The winners! 🏆 #Vuejs #nuxt #vue #Toronto #VueConfToronto2024 #VueToronto

@AlPalVipond I agree with that too — though there are lots of attributes that don’t follow that pattern. I think html/aria tend to lean on brevity as a design principle

@thedamon That makes sense, I read the spec some more this afternoon and had that same thought. I kind of have the opposite opinion about detailedby though—if they had gone with that instead of details, it would have been a nice, explicit hint about how the feature works

aria-label: accessible label aria-labelledby: id of element that contains label aria-description: accessible description aria-describedby: id of element that contains description aria-details: id of element that contains details aria-detailedby: not a thing WHY

@NotionHQ can i have locations for events that are in Notion databases? i've been wanting this, but i added a location field to my database and it's not showing in Notion Calendar

@Zayne_kayden @AlPalVipond @vuejs Really the <tag> itself should be a different color if there’s a v-if or a v-for on it (and those directives should be that same color)

@Zayne_kayden @AlPalVipond @vuejs I agree with overpowered attribute not being the ideal syntax for control structures. I kinda wish it was at least its own tag <v-if> (which can be done w custom comp but a bit silly). Though — this could largely be mitigated with better syntax highlighting

A thought floating around in my head: I like @vuejs because it's such a nice balance between productivity and art. All of its internals are very well scoped and abstracted. Programming aesthetics are sacrificed when the productivity payoff is big enough.

@AlPalVipond This boils it down well. Options API is a hand to hold. Feels a bit mean to take that away!

Learning Laravel changed my mind about the Vue Options API. I will never use the Options API again, and I hope Vue will never stop supporting it.

@MichaelThiessen @vuejs @nuxt_js Also useful for accessibility!!

@AlPalVipond I am always tempted that way too, but same sticking point. We ended up with a lot of extending a base component and changing prop defaults, which is kinda weird but worked pretty well — extends is super uncool these days though.

I'm tempted to do all visual changes with `variant`, and all logic or pre-configured behavior stuff with wrapper components. When the visual change involves additional markup though, I usually get stuck

When you own your design system (e.g. it's React Aria, shadcn/ui etc.) and you need to create one-off variants for certain components, what's your approach? Some examples: - Password input with strength indicator - Country code number input - Button with notification dot

@sarah_edo @SheCodeAfrica This is amazing news! 🥳 Thank you

@thedamon @SheCodeAfrica It’s coming! It’s in review now

🎉 It’s happeninggg!!! Engineering Management for the Rest of Us is now on sale! I’m so excited to finally release this after so much went into it. 50% of all of my profits will go to She Code Africa! @SheCodeAfrica amazon.com/Engineering-Ma…

@MichaelThiessen @inspiretim24 @vuejs I know about keys for sure (and used the outside loops to force updates occasionally).. I just never ran into a recommendation to use them generally on ifs and elses tho I do kinda see it now that I look for them specifically. Feeling like a mandala effect ahaha

@thedamon @inspiretim24 @vuejs #Controlling-Reusable-Elements-with-key" target="_blank" rel="nofollow noopener">v2.vuejs.org/v2/guide/condi… I've also had cases with transitions where adding a unique key was necessary. Not sure if that case is fixed now too — haven't had a chance to check that out for awhile.

In your opinion, what is the best new feature that @vuejs has added recently? Or maybe it's an upcoming feature that you're excited for?

@inspiretim24 @MichaelThiessen @vuejs I’ve never put a key on an v-if/v-else just v-for … did I miss something?

@MichaelThiessen @vuejs defineModel. $attrs now includes class and style. keys no longer necessary on v-if/v-else branches as Vue now autogenerates them.