0 days since I last took down production
0 days since I last took down production
Maybe I'm weird, but I've always preferred learning by doing over learning by watching a tutorial video.
I don't think I've ever followed a tutorial from start to finish.
Apparently a hot take: If you're already paying an agency a lot of money to do custom development on your theme, you're better off with Hydrogen.
Bernie should have run against Trump first time around
Date strikes again. Though I was surprised by this one because it was using a historical timestamp. But the `toLocaleDateString` apparently behaved differently in server/client even though the locale was defined.
It's the only option the Democrats have if they want to remain relevant. There are voices within the Democratic party that can lead the way, and they have been ever since inauguration day.
My electorate is a safe electorate, so I already know where my preference will flow in the end. But I'll put some other candidates above just to show discontent I guess.
Hoping for a continued rise in independents to challenge the current status quo.
We use preferential voting here, so you number the candidates in your electorate from 1 - Last. If your 1 doesn't make it past the ballot, they check your 2 and so on.
This has put a lot of independents in parliament in the past decade. A way to show the major parties they need to change.
The Democrats lost the election more than the Republicans won it.
From a European's perspective, the Democrats are far from left. They have a few left-leaning policies, but they're still a party for the rich. They just slow down the rising wealth disparity, but do nothing to fix it.
Invoicing day! ๐ฐ
We have our own Trump-lite, a.k.a Lord Voldemort, a.k.a. Mr Potato Head. He tried to run on a similar campaign (DOGE etc), but it's backfired and he's been forced to spend most of the campaign backtracking. We'll see how this translates when echo chambers fail to report it, or make up excuses.
100%! Somewhat similar over here as well (our election is coming up this weekend). Neither of the major parties mention who's been getting richer while everyone else has been getting poorer.
All the talk about inflation forgets to mention that someone reaps the rewards of higher prices.
Head on the nail there, mate. A big problem with echo chambers is that people get trapped and bombarded with distractions designed to make them not realise the real issues.
"People can't afford housing or food, and I lost my job to AI."
...
"Look, a trans person in the women's bathroom!"
I worry about echo chambers sometimes. I used to feel hopeful about humanity's future. Then I realised the algorithms weren't showing me the nonsense when a certain orange clown got elected across the pond.
At the same time, I'm happy I don't see too much of that rubbish, I'd go mad.
Debugging Hydration mismatch errors and having fun
Or not
did you ask it to list what it's done in the past week?
Wow, nearly one in three OT games goes to shootout. That's more than I thought
And a lot more entertaining! Yeah, I'm torn on the loser point. Going with a 3-2-1 point system like the Swedish league does is an option, but it can really make the top teams run away with it, killing off the playoff race too early
I've been having too much fun with Hydrogen and Sanity to post in a while
Agree! I'd rather the game ends on a tie after 10 mins OT than let the extra point be awarded to the winner of a skills comp
Figured out a solution to this. In the GROQ query, you can concatenate the string with an empty string, seems to throw stega off so it doesn't get appended.
E.g. 'alignment': '' + alignment
The poor DX in theme dev leads to high attrition. Talented devs stay clear of ecom, or get out as soon as they can.
Talk to recruiters for other dev fields and you'll soon find out how the industry sees ecom.
This needs to change.
2/2
I split my weeks between headless and theme development, and let me tell you, they're polar opposites. One has a great DX and allows for modern dev practices, while the other is extremely error-prone and leads to many headaches.
I would quit ecom if I had to work in themes exclusively
1/2
Could you opt out of stega encoding on subfields? This value never needs to be mapped to the studio. Or should I just not use a string in the first place and work out a different solution?
So now I'm stuck with either adding a dependency to stegaClean from @sanity/client/stega or hoping that this regex covers all possible issues: /[\u200B-\u200D\uFEFF]/g
Inspecting the source for stegaClean, it in turn has a dependency to a vercel package with a much more complex regex
Found out why: www.sanity.io/answers/issu...
Stega adds zero width space characters for mapping in preview sessions. That wouldn't be an issue if I wasn't using this value for placement, which needs to work properly in preview sessions too
So turns out it's because the alignment value has *a lot* of zero-width-space characters appended to it.
I thought maybe copilot was playing tricks on me. So I deleted the values from the Sanity schema and entered it manually.
Nope, still getting it.
Console logs showing JS not able to match a string with the value center to another string with the value center
What is going on here? JavaScript, you're drunk!
Having lots of fun doing it and getting to try all the latest Sanity features in the process.
Presenting the proof of concept on Tuesday to sell the full project. Wish me luck!
Worst case scenario I've wasted a week and a half. Best case I walk out of there with some more $$$ and a happy client
Trying to see how fast I can rebuild a site with Hydrogen using my recipe collection. The site is already headless, so I can reuse a fair bit. But it uses Chakra and Gatsby on the frontend, and I'm all in on Tailwind. Plus the Sanity schema is a mess and the Studio is V2, so an upgrade is in order