Grape VS TTY

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

Few days ago I've created a script for the project I'm working on. It was an ugly script with hardcoded values, but it did ther job - create tokens on request. But I've decided to improve it a bit, because sometimes I needed to change params and I've added ability to submit params from the command line. Of course, there are a lot of awesome libraries such as dry-cli, TTY Toolkit or cli-kit from Shopify, but in most cases you can use standard ruby libraries like OptionParser or GetoptLong. Lets see how you can create a CLI utils with those libraries just in few minutes.

Not curses but something Ruby style: https://ttytoolkit.org/. No C dependencies, I think...

TTY-ruby is an extensive CLI toolkit that might help you do what you want. Have a look. I’ve used some of them successfully in the past.

TUI? Terminal UI? If so, check out https://ttytoolkit.org/ and https://github.com/Shopify/cli-ui

Saw just now. Cobra is huge and offers a lot. Btw, I've used this https://github.com/piotrmurach/tty for a Ruby project a while ago and was looking for something similar. I guess Cobra it is. Thanks again!

If you're interested in taking things further, maybe have a look at Build Awesome Command-Line Applications in Ruby 2. If you're not ready to buy a book, check out the Ruby TTY Toolkit page.

The tty suite of tools are a good shout, although I've never used them in anger. https://ttytoolkit.org

TTY::Box provides box drawing component for TTY toolkit. 142 stars by now