I am planning for an API app in Rails using Grape micro-framework. Is it a good idea to use Grape with Rails. Are there any prerequisites that I should take care of?
相关问题
- Question marks after images and js/css files in ra
- Using :remote => true with hover event
- Eager-loading association count with Arel (Rails 3
- Google places autocomplete suggestion without coun
- Is there a way to remove IDV Tags from an AIFF fil
相关文章
- 我用scrapy写了一个蛮简单的爬虫怎么封装成一个api啊
- 后端给前端的API接口是怎么用代码写的
- Right way to deploy Rails + Puma + Postgres app to
- AWS S3 in rails - how to set the s3_signature_vers
- how to call a active record named scope with a str
- How to add a JSON column in MySQL with Rails 5 Mig
- “No explicit conversion of Symbol into String” for
- form_for wrong number of arguments in rails 4
Depends on your long term goal of what you are planning to do with your API. If you want to make a stable API and maintain that for the long term use, I don't recommend grape (from my personal experience). I have used grape in one big project, and it was too hard to work with it when it comes to customizations e.g. handing exceptions etc. Instead you should consider using ActiveModelSerializer or jbuilder. I personally moved to ActiveModelSerializer from Grape, and was happy at the end. grape is good for building your API quickly as it provides a decent DSL, but in the long run, it was hard to maintain and add new features and customizations. So, it really depends on your long term goal.