Skip to main content

Explain sinatra route

* Sinatra is simply a Ruby Gem that is build specifically for easy web development. Its syntax is generally build around blocks like one below.

get '/' do
    @value = 'abc'
    erb :layout
end

 -sinatra route derived its name from HTTP method like GET, POST, or PUT.
- here, '/' means a route for the web application like www.yourapp.com/ , it just specify the last character '/' for brevity.
- any instance variable like @value will be accessible inside the templating language , in this case, erb file.
- The last line 'erb :layout' will ask Sinatra to execute the template :layout


* There are two important variable in Sinatra, namely params and session
- session is instructing Sinatra to build a cookie that holds important information/build states that will last between multiple HTTP request, since HTTP is a stateless communication (ie. it forgets after each HTTP request).
- You can push any information any information into session because it is just a  hash. eg:

 session[:success] = "Successful ! "

- You have to enable session before using it like this:

 configure do
  enable :sessions
  set :session_secret, 'secret'

end

- it appears to me that session is unique between route, but i could be wrong.

* params
- params is a universal variable that is unique inside each sinatra route block

get "/link/:id/:num" do
  @value = params[:num]
  erb :layout
end

- This will create a params hash of { :id = "value1", :num = "value2" }
- params is unique for each route block.
- if you have a form, the form input will have a data inside the params hash.

www.yourapp.com/link?name=john

The above URL contains a query and will create a params hash with a key of 'name' and value of 'john'. 


Labels:

Comments

Post a Comment

Popular posts from this blog

Problem Solving - Refactored

I am going to outline how I approach problem solving. The relative importance and the amount of effort/time required for each is stated as a percentage beside each topic. I borrowed some idea from George Polya's How to Solve It Thoroughly Understand the Problem (30%) When encountering hard problem , you need to deeply understand the problem at hand. Take a paper and list down all known facts and data and what the question is trying to find. Sketch out the problem if applicable. Visualize the problem in your head. A lot of times, we only have to understand the problem well, then the solution will obvious. Have a Plan (20%) You need to have an outline of how you are going to tackle the problem. You need to have a logical pathway that will ultimate produce outcome (nothing to do with coding syntax yet). Without a plan, you are just randomly poking around and got lucky. No hard problem ever gets solved without a plan. Plan using pseudo-code, pen & paper or flowchart. Use wh...
5 comments
Read more

Sharing my Weakness

It makes sense to know about your weakness and do something about it. Here are my known weaknesses uncovered during my time in Launch School. 1. I don't like to refactor my code   - Your first draft will not be perfect. It works but it may not be efficient/readable/best practices. You final code will almost always be better than your first draft. - It is easier to separate the task between writing code that works and refactor later to make it efficient/readable/best practices. - If you refactor your code often, over time you will discover your bad habits and change it. 2. I don't like to read other people's code - There are more good programming practices in other people than in you (especially for beginners like me). - To be good , you need to know more than one pathways to solve a programming problem (and there are always more than one way). Then you can judge their merit. - Reason for dislikes    1. It is considerably harder to read code than to write one (...
1 comment
Read more

Static vs Relative vs Absolute vs Fixed

Static: the default position. Everything starts from top to bottom nicely according the document flow. Relative: still within normal flow of document. But accept offset position, relative to its original document flow position Absolute: out of normal flow. It doesn't interact with elements around it anymore. The reference point will be parent element that has relative positioning, if not, reference body element. Accepts offset position Fixed: out of normal flow. The element sticks to a corner of the page even if user scrolls. Reference the windows view.
Post a Comment
Read more