Grape VS FriendlyId

Grape’s support extends to standard conventions, multiple format support, content negotiation, versioning, etc. The complete guide to Grape to develop REST-APIs, test the API and analyze the performance metrics is available on its official GitHub page.

Grape (ruby-grape.org)

I'm very ambivalent about Grape, but this very much reminds me of something I do really like about it: the param validation. https://github.com/ruby-grape/grape#parameters

I am currently working on developing and api using grape and devise jwt for user user authentication.

Your RN app will be making http requests to your server, so it doesn't really matter what backend language/framework you use. If your React work was also utilizing http requests to fetch data, then there shouldn't be much of a difference. If your backend is a simple JSON api, checkout Grape. You can tack it on to any existing Rails app.

I've benchmarked Grape with YJIT and without it (if want to see the code, visit repo)

Grape is a REST-like microframework written in Ruby programming language. Grape is also considered among the best ruby frameworks and can be used to run on top of Rack or can be used to complement the existing web application frameworks such as Sinatra or Rails. The latter can be done through the DSL-based REST-API for communication. The Grape ruby web framework facilitates efficient and meaningful APIs working in the web application domain.

Take a look at Grape - https://github.com/ruby-grape/grape

I love the Grape gem for building APIs - might be worth considering if you are building something new: https://github.com/ruby-grape/grape

Grape is a REST-like API framework for Ruby. It’s designed to run on Rack or complement existing web application frameworks such as Rails and Sinatra by providing a simple DSL to easily develop RESTful APIs. 9,200 stars by now

On a side note, "Sqids ... is an open-source library that lets you generate YouTube-looking IDs from numbers.", "The main use of Sqids is purely visual."

If the purpose of it is to give a friendlier url / id, who not use something like friendly_id instead? (http://norman.github.io/friendly_id).

The url is readable and searchable through the history.

I would much rather prefer people using "www.website.com/channel/video/a-dog-walking" instead of "www.website.com/channel/video/3cXv8c".

Take a look at https://github.com/norman/friendly_id for a good gem to implement them.

Check out the friendly_id gem! I remember watching a GoRails video about it and thinking it looked super easy to implement.

SEO tools - meta-tags, sitemap_generator and friendly_id

friendly_id - We will use the friendly_id gem, which created slugs that we can map to a predetermined route. This is a method you can use throughout an application, not just with the User models.

FriendlyId is the “Swiss Army bulldozer” of slugging and permalink plugins for ActiveRecord. It allows you to create pretty URL’s and work with human-friendly strings as if they were numeric ids for ActiveRecord models. 5,500 stars by now