@dhh Do you also book a dentist appointment for the Monday after? 😅
English
Dan Gamble
4.3K posts
Dan Gamble
@_DanGamble
CTO @ @bao_agency Shopify Plus agency 🤙. Forever with me @breadedwheat :)
Katılım Ocak 2011
318 Takip Edilen606 Takipçiler
English
@_DanGamble @miacmal @CloudflareDev @_DanGamble No plans to increase max D1 database size. Message here or via vy@cloudflare.com what your needs might be - we're exploring different options across our application data storage products.
English
we’re steppin up our workflow limits @CloudflareDev
maximum steps per workflow: 1,024 -> 10,000 by default, configurable up to 25,000
English
@dok2001 @joeychilson Would love to know what this means as I absolutely love the bindings and everything it enables 😅
English
I wish this was true, but wrangler and bindings are holding Cloudflare back so much.
I don't want to fundamentally change how I write apps just to be able to deploy on Cloudflare.
Get rid of it completely.
Dane Knecht 🦭@dok2001
So good bye to wrangler.json
English
what page should we do next?
Dan Gamble@_DanGamble
The workflow pages on @CloudflareDev are sexy as fuck
English
@SammyIsseyegh What's been your use case for it? I have a mega idea I want to use them for with meta objects but it keeps destroying my brain trying to plan/map it all out
English
@SammyIsseyegh Transactions would be a huge/pretty needed add. I also think `references` and `referencedBy` should be able to take a query/be able to filter for the resource you want so you don't get _everything_ back then need to filter it
English
My main concern with this is that nested metaobjects - even one level deep, become almost impossible to manage.
Everything has to be sequential etc. How do you recover from a network failure? How do you handle cleanup/what if cleanup fails?
Using the JSON type, removes all of that complexity - it's all done in one `metafieldSet` call and the consumption in liquid feels....the same?
Patrick Jakubik@patjakubik
Shopify sets new metafield limit to 16 KB (previously 2 MB for JSON and 64 KB for others) and no one is talking about it? This is really bad.
English
NEW: Automate your dev store setup (and so much more) from Shopify CLI!
Check out some examples and tell us about your plans to use these new commands:
community.shopify.dev/t/admin-api-an…
Shopify Developers@ShopifyDevs
Query and manipulate dev stores from Shopify CLI Execute queries, mutations, and bulk operations from your terminal Script it, automate it, or hand it off to an agent
English
this is huge: and it also applies to Workflows.
long running or more complex Workflows can now make up to 10 million sub-requests per invocation.
Mike Nomitch@MikeNomitch_CF
Thrilled about this change to Workers. Each Workers request can now make WAY more subrequests. Previously, it was capped at 1000, which could be tough if you had long-running Websockets or Workflows. Not an issue any more...
English
@dhh @George_Kurtz Completely fair. Only been sim racing so have zero real life experience but downforce scares the fuck outta me 😂. So hard to adapt to and constantly under drive the car which in turns makes it worse as you're not getting the most downforce
English
@_DanGamble @George_Kurtz My drug is downforce. LMP2 has a lot more of it than GT3s.
English
Three minutes of me driving around the GTs, passing P2s, spinning @George_Kurtz, and going three wide at ~300 km/h in turn 1 at the Daytona Rolex 24 with the Shopify #11 LMP2. Pure flow at the edge of adhesion!
English
@_DanGamble Mine is dumber than that — it just renders the Mermaid to SVG via CLI and then injects that SVG into the TLDraw canvas. That’s why I call it beaming/projecting because it’s just a display mechanism.
English
@rjs is your beam tool anywhere? Tried to get Claude to recreate it but it is struggling _hard_ 😅
English
@rjs This is fascinating. I just tried it in OpenCode. Really liked the results. I then figured I'd give CC a go and try and use the new agents piece as well but the results were _so_ much worse with the same prompt. Output is much prettier in CC though!
English
@FORSBERGtwo @dave_cameron I tried to get that working but had no luck! Unfortunately I don't use VSCode either but did try to get it working in that. My LLM is worse than yours apparently 😂
English
@dave_cameron @_DanGamble Seems most Web Component libraries use the following feature of VS Code to ship auto-completion to any HTML aware language, as part of the library: webcomponents.dev/docs/vscode-cu…
I created a prototype by extracting all the properties using an LLM, and it works nicely so far 😎
English
Just deployed the first version of our "Setup Guide" for Orderly Emails. Still some things to improve, like adding sub-steps to customization steps, but great to have it out 😎
Fun challenge using Polaris Web Components together with a Turbo frame and streams for state changes.
English
@dave_cameron @FORSBERGtwo To be fair I found this when using it with Rails. That was more down to the autocomplete you get when using it with TypeScript and how used to that I got. Having zero autocomplete makes it harder to remember. With that said, once you're used to the API it does feel simple to me
English
@FORSBERGtwo @_DanGamble How could we improve that with our Polaris docs Björn?
English
@FORSBERGtwo The thing I was looking to test with it was creating the discount UI as it is something we have to do quite a lot. For example adding a discount code, the sidebar updates too. I was thinking of having server side state and constantly reloading frames with that
English
Was actually pretty easy. Guide is wrapped in a turbo frame, so any onboarding update actions just redirect to onboarding show page, and then the UI updates seamlessly. Also added after_update callback in model to call a custom “reload turbo frame” stream action, so when db state changes it syncs to the UI just by reloading the frame 😊 Very little UI work really, other than trying to get my head around Polaris Web Component properties.
English