globalid VS turbo-rails

If you are solely linking to resources within your application, you should read on and consider using Rails Global Id. It also handles expiry, we've used them at every Rails company I've worked at. Best part is you don't need to worry about storing them in your DB.

As for the issue with context, I think it's also solvable I think. And passing for example current_user (or current_user_id) would be possible. Probably with this https://github.com/rails/globalid

You could use a signed GlobalID for this, which would also give you the ability to generate URLs that expire. https://github.com/rails/globalid

did something similar, I ended up using a globalid as the parameter to the job, and the globalid had a parameter with the database name

to_gid_param generates the Global ID for a model and then Base64 encodes it. For strings, to_param returns the object itself. For symbols, it returns the object's string representation.

Hi guys, I want to know if it is possible to generate a signed global_id string, for example like this "BAhJIh5naWQ6Ly9pZGluYWlkaS9Vc2VyLzM5NTk5BjoGRVQ=--81d7358dd5ee2ca33189bb404592df5e8d11420e" and then shorten it, and then return it to its original state. I need to track a record by an "ID" and I was thinking signed global_id is great but it's too long I'm thinking something no longer than 20 characters, the other option I thought of is a UUID, and then encode it to some base like 32 or 58 maybe?, but it misses the awesomeness of the global id. What advice do you recommend to obtain a short string that allows me to share it and track a record? https://github.com/rails/globalid

You can test this be getting the Global ID of a user and going to the endpoint.

Ruby/Rails has this in the form of GlobalID[1]. To be honest I haven't seen it used outside of whatever Rails itself automatically does, but the concept is there.

[1]https://github.com/rails/globalid

The install notes here link to an issue specific to webpacker. Try that and see if it works?

True, in theory it is. A lot of it is coded in libraries like turbo-rails, though. And these are Rails-specific. But I've seen it being used in some Laravel projects, also I used it with Hanami.

Check out https://github.com/hotwired/turbo-rails/blob/main/app/models/turbo/streams/tag_builder.rb

So apart from the pretty obvious question of "why on earth would you want to do this?", I think there's a misunderstanding here of the intended use case of turbo streams. You have a page, and then some state changes on the server and you want to update the page to reflect that. Incrementing a variable doesn't really qualify as a state change, but perhaps a Product changing from "not good" to "good" would be an event worth broadcasting, which you could do using the Broadcastable concern in turbo-rails.

Use this too: https://github.com/hotwired/turbo-rails

Not mentioned in the article, but it's nice that turbo-rails recently gained the ability to pass ViewComponent objects directly to turbo stream helpers. https://github.com/hotwired/turbo-rails/pull/433

Release notes: https://github.com/hotwired/turbo-rails/releases/tag/v1.4.0

turbo/streams_channel.rb - a way to link a turbo stream with an ActionCable channel.

The readme seems to give a pretty good overview of turbo: https://github.com/hotwired/turbo-rails