graphql VS sdoc

My memory is fuzzy, but...

1. all data flow through the rails app (no pre-signed s3 upload or download links for direct uploading).

2. no support for CDNs (I think newer rails versions added support)

3. blobs and attachments were unnecessary abstractions.

3a. Querying was annoying and easy to add n+1 queries.

3b. Images are moderated and it was unclear where to put the moderation metadata (on blobs? attachments? create a new table? why so many tables?). Accessing the data was annoying (you need extra joins).

4. GraphQL gem didn't support it: https://github.com/rmosolgo/graphql-ruby/issues/1777

In our Rails application, we use the popular graphql Ruby gem to resolve GraphQL queries. When used naively, it essentially resolves queries as a depth-first tree traversal, which leads to the N+1 problem in GraphQL.

If you're comfortable on the react/client side with graphql, I'd highly recommend plugging in https://graphql-ruby.org/

We use GraphQL, and Ruby GraphQL doesn't allow you to stream the result, it buffers it before sending back the request and there are no alternative. See my issue https://github.com/rmosolgo/graphql-ruby/issues/3969 -- Sadly there is only one library for GraphQL in Ruby.

graphql-ruby is a Ruby gem that implements the GraphQL specification and functionalities.

The next step is to add the GraphQL gem to our Gemfile; you can visit its page, graphql-ruby, for more details; now, open your Gemfile and add this line:

If you do go the API route though, strongly consider using GraphQL with the (graphql-ruby)[https://graphql-ruby.org/] gem.

GraphQL saves you time designing versioned REST endpoints. It self documents. Documentation isn't optional for serious web development so this is a huge win. The rails gems have gotten really good at picking up associations as well since I looked into a couple years ago. https://graphql-ruby.org

When it comes to implementing a GraphQL server in Rails, one can use the excellent GraphQL Ruby gem.

Once you feel comfortable with both Ruby and Rails, try building a few simple apps on your own by reading the Rails Guides and browsing the Rails API whenever you're stuck.

Hi. I'm a self-taught Ruby on Rails programmer. I have a question about the documentation at https://api.rubyonrails.org. On many of the pages, you'll see methods and their details. Below that, you'll often see examples using different options. This is where I have a question. An example might look like this:

If a method isn't documented in https://api.rubyonrails.org/ it shouldn't be used as we reserve the right to remove or change them at any point.

Rails still holds the top spot in getting things out the door in the shortest amount of time. So many example projects and tons of amazing libraries that are available. They absolutely have the best developer docs in the industry as far as I'm concerned.

https://guides.rubyonrails.org/

https://api.rubyonrails.org/

Phoenix/Liveview is a close second. I would personally use Phoenix/Liveview at this point because since I know that stack pretty well, but it is definitely not as easy as Rails to learn. However, once past the learning phase I think there's distinct advantages especially with Liveview.

Fly.io has a free hosting tier currently. You can also get some free servers through Oracle Cloud.

https://api.rubyonrails.org is your best friend. Check the docs before googling. Instant access to the source of functions. ApiDock is shit but continuously gets to the top of google search results.

For something more in-depth, besides the Rails Guides that have been mentioned already, you could also use the Rails API docs as a reference.

Yeah visit guides.rubyonrails.org if you want to see how to do a particular thing like validations and stuff and use this website https://api.rubyonrails.org/ for seeing method definitions their options etc.. These two websites pretty much conver everything. I specially use the second on pretty frequently. Also I think sublime text is better for ruby on rails than vs code but thats personal preference. The ruby doc website is pretty good to for documentation on rubies standard classes. Like if you are looking for some method to do something for a string you can just search string ruby and this comes up first, it contains all public methods for these classes and is pretty useful.

If you mean the Rails API Documentation, I mainly use it when I use a method I'm not familiar with (eg trying to adapt a StackOverflow suggestion).