@AmandaBPerino I started picking up the Zed editor with Vim mode. It's a good editor with some AI features. E.g. Zed started supporting custom MCP servers, which I started using to build some small custom ruby/rails "AI" commands I can preconfigure:
Welp the day has come that the company I worked for got sunset so I am on the hunt for a new job. If anyone happens to know of any great Rails shops(that use turbo 🤞) feel free to reach out! DMs are open. RTs for reach appreciated.
@rossta Great idea! Two questions:
Is there a production ready FTS and vector similarity search :)
Last time I checked it there were some bigger issues with fts and vector plugins were really early in development.
@JasonSwett I've built a Rubocop cop disallowing TODO, WIP etc. comments. I have the same experience with TODO comments. Open tasks should be not tracked in the source code.
@readjosefarias No, unfortunately not. I use emails a lot for sharing stuff between non apple devices. Not as convenient though as the Universal Clipboard (but good enough most of the times) :D
@johnlpollard@domchristie I prefer tag.<tagname> so I don't have to remember if an element is a void element. E.g `content_tag('img')` vs. `tag.img`.
Also I try to avoid calling raw, html_safe and friends unless absolutely necessary, because every usage can introduce XSS.
@strzibnyj I prefer fixtures as well. Way faster, good sample/dev data, no callbacks when seeding devdata. I think a lot of devs are used to an empty database in each individual test case and this not being the case puts them off at first.
I just realized ActiveStorage's :resolve_model_to_route config can be configured with any custom url helper name, including but not limited! to `:rails_storage_proxy`
@_swanson I like the default and the `why` comment and love the general naming.
I'd try to get rid of the `next if` by filtering them in `relevant_participants` or a similar method. I don't hate it though.
I'd do `if: [:save_change_to_locked?, :unlocked? ...]`
Nice snippet!
@Shpigford I'd go for the Rails MemoryStore. It's available by default. Basically configure in production.rb:
`config.cache_store = :memory_store`
And the cache code:
```ruby
def fetch_stargazer_count
Rails.cache.fetch("stars", expires_in: 12.hours) { Github.fetch_stars.to_i }
end
```
Today the Rails Foundation welcomes our first German member: @makandra_de. makandra has over 15 years experience building Rails applications for a range of companies from small one-man operations to corporations as large as Volkswagen and Audi. We're proud to have them as a Contributing member! More here: https://t.co/Odk4dqHMK9
It will parse the browser' importmap, register custom elements based on the filename making them available in your Rails app without any build step.
E.g. `hello_element.js` will register `<app-hello>`.
Check it out: https://t.co/UhUrD1UxZ2