learn-co-curriculum / sinatra-basics Goto Github PK

We should either separate these into a new repo for later reading OR mark these sections of advanced. This is too much for someone new to Sinatra to understand.
@AnnJohn @ipc103

There is a bit of overlap in this reading and the previous readingin the Learn Track, and some of the content mentioned in this reading- such as controllers- might be better placed in the previous reading.

As a suggestion, can the previous reading focus on single file Sinatra apps and really give the student a sense of the file structure as well as examples of single file apps.

This reading should focus more on defining modular Sinatra apps, why we use them, and clear examples of it. It should definitely distinguish it from the single file apps. I didn't get this sense from the reading. Attention wouldn't need to be devoted to the controllers (except for the mounting part in config.ru) since it would be covered in the previous lesson.

Also how do I run a modular Sinatra app? Is it the same way as running a single file app?

@jmburges

Give an example of naming your class MyTodoApp or something like that. Also show the error that happens if your class name doesn't match the thing you try and run

^^ would be helpful to simplify this just a little single "Modular Sinatra Pattern (over the single file app.rb)" doesn't provide much context.

^^ "ruby class Application, which is defined in app.rb" is a bit confusing.

^^ Inheritance hasn't been discussed in any of the previous readmes, as well as what a Rack-compatible interface is. Also, what is Sinatra::Base?

^^ Will students understand "sinatra routing DSL?"

^^ Can this be shown via code snippets?

cc @matbalez

"This inheritance transforms into a web application..."