I guess it's time to migrate to Bridgetown 🙂
I guess it's time to migrate to Bridgetown 🙂
docs.ruby-lang.org/en/master/
Thank you @st0012.dev and the entire team contributing to RDoc for these improvements.
docs.ruby-lang.org/en/master/
Thank you @st0012.dev and the entire team contributing to RDoc for these improvements.
We're not using distinct naming, which makes it harder to decouple from Bootstrap. I think this plus components is our ticket out of those legacy shackles.
BTW, you're missing a Bluesky profile link 😉
We're not using distinct naming, which makes it harder to decouple from Bootstrap. I think this plus components is our ticket out of those legacy shackles.
BTW, you're missing a Bluesky profile link 😉
You don't? Well, I do 😄 So, I thought it would be cool if Ruby LSP could autocomplete schema statements in migrations ✨
github.com/Shopify/ruby...
You don't? Well, I do 😄 So, I thought it would be cool if Ruby LSP could autocomplete schema statements in migrations ✨
github.com/Shopify/ruby...
www.zolkos.com/2025/12/03/v...
We use a lot of these techniques in Web Awesome.
Color-mix, :has, css nesting, layers, etc
CSS and HTML continue to get more and more powerful , and we all benefit as a result.
A rising tide lifts all boats.
www.zolkos.com/2025/12/03/v...
We use a lot of these techniques in Web Awesome.
Color-mix, :has, css nesting, layers, etc
CSS and HTML continue to get more and more powerful , and we all benefit as a result.
A rising tide lifts all boats.
However, having trouble detecting whether I'm in a migration file. E.g. for `class CreateUsers < AR::Migration[8.1]`, `index.resolve("CreateUsers", []).parent_class` returns `::Object`.
However, having trouble detecting whether I'm in a migration file. E.g. for `class CreateUsers < AR::Migration[8.1]`, `index.resolve("CreateUsers", []).parent_class` returns `::Object`.
I haven't used YARD in any of my gems, and stdlib doesn't use it. I believe YARD annotations are powerful, but aiming for (inline) RBS seems more future-proof.
I haven't used YARD in any of my gems, and stdlib doesn't use it. I believe YARD annotations are powerful, but aiming for (inline) RBS seems more future-proof.
I found it interesting how Ruby LSP's indexer is written almost as a separate gem, I'm curious what the reworked indexer will improve.
I found it interesting how Ruby LSP's indexer is written almost as a separate gem, I'm curious what the reworked indexer will improve.
I'm considering buying Tailwind Plus almost exclusively for that library, as we don't use React/Vue.
I'm considering buying Tailwind Plus almost exclusively for that library, as we don't use React/Vue.
github.com/Shopify/ruby...
github.com/Shopify/ruby...
github.com/Shopify/ruby...
github.com/Shopify/ruby...
github.com/Shopify/ruby...
github.com/Shopify/ruby...
The biggest release yet, packed with new language bindings, Linter Autofix support, Linter Fix-on-Save, a new `.herb.yml` config file, formatter improvements, Tailwind Class Sorting integration, and a ton of performance, tooling and LSP improvements! 🌿
The biggest release yet, packed with new language bindings, Linter Autofix support, Linter Fix-on-Save, a new `.herb.yml` config file, formatter improvements, Tailwind Class Sorting integration, and a ton of performance, tooling and LSP improvements! 🌿
You can find full release notes at github.com/zed-extensio...
You can find full release notes at github.com/zed-extensio...
Here is a demo of that working in @zed.dev using the new `.herb.yml` configuration file! 😍
Here is a demo of that working in @zed.dev using the new `.herb.yml` configuration file! 😍
Huge thanks to @bernsteinbear.com for the JIT mentorship and nomination, @k0kubun.com for years of guidance, and everyone who supported me along the way.
Looking forward to improving Ruby and its DX!
Huge thanks to @bernsteinbear.com for the JIT mentorship and nomination, @k0kubun.com for years of guidance, and everyone who supported me along the way.
Looking forward to improving Ruby and its DX!
Sorbet’s RBI was way too verbose, as it had to be valid Ruby, but at least it was inline. RBS was more compact, but required separate files.
Inline RBS is just comments, and I imagine it has advantages over YARD.
Sorbet’s RBI was way too verbose, as it had to be valid Ruby, but at least it was inline. RBS was more compact, but required separate files.
Inline RBS is just comments, and I imagine it has advantages over YARD.
They have just unlocked for me recently. It started with a contribution to Stimulus LSP, afterwards I wanted to fix issues I've been experiencing with Ruby LSP.
Kudos to Shopify for solving difficult problems like indexing 🙇♂️
They have just unlocked for me recently. It started with a contribution to Stimulus LSP, afterwards I wanted to fix issues I've been experiencing with Ruby LSP.
Kudos to Shopify for solving difficult problems like indexing 🙇♂️
Rails.vim had a neat feature where you can follow render calls in view templates via `gf`. I'm exploring adding the same feature to Ruby LSP Rails via "go to definition" 🤞
Rails.vim had a neat feature where you can follow render calls in view templates via `gf`. I'm exploring adding the same feature to Ruby LSP Rails via "go to definition" 🤞
That's really a killer feature, both Chamber and AnyConfig support it.
That's really a killer feature, both Chamber and AnyConfig support it.
1. returns malformed results for method aliases
2. doesn't support request cancellation (Zed doesn't debounce atm)
3. searches gems as well, which is 3.5x slower, and adds up because of 2.
1. returns malformed results for method aliases
2. doesn't support request cancellation (Zed doesn't debounce atm)
3. searches gems as well, which is 3.5x slower, and adds up because of 2.