My first app. How should I approach this association thing?

Hi people. I’m a newbie so bare with me :stuck_out_tongue:

This is my first rails application: . It’s
app where visitors have the ability to see Offers submitted from
These Offers also belong to Categories. So Offers, Vendors and
are the models & resources in my application.

Until now I implemented these pages:

and now the important part: I want in the vendor pages
( where all the Vendor’s offers are listed, to
have a
sidemenu which will have all the Vendor’s offers grouped by categories.
the visitor will be able not only to see all the Offers from Vendor A,
all the Offers from Vendor A and in Category A, B or C.

Thing is, I don’t know how to generally approach this issue. How should
route this? Should I add a sidebar partial template that will render the
category menu? Should the routes be like
or maybe I should use query parameters like

What would be the Rails way of doing this?


Also, what about the controllers? Would I need all of them? Right now I
have 3.

I’m just thinking now, maybe the whole approach (following the RESTful
architecture) isn’t the best choice for my app. Could I maybe do

Since you are very new to Rails, I would suggest that you take a an hour
two to go through a three step approach to gather the knowledge you’ll
to answer this yourself.

  1. Use the Rails scaffolding feature to build out the models,
    views and tests for each of your models. A lot of this code you will
    up not using and/or modifying heavily, but it gives you a place to start
    and should help you to get more comfortable with the “restful” approach.
  2. Identify the ActiveRecord relationships you will need between your
    models. Implement those model relationships. (
    Use IRB to build some records and test model relationships. ( )
    queries/scopes in your models, and test them also in IRB. ( )
  3. Implement the routes and nesting that make sense now that your
    and relationships are established. ( , Based on
    relationships/routing/nesting you implement, you will see what
    and views you will need to build out.

When I am starting a new, complex project, I will oftentimes go through
this three step process two or three times, taking a slightly different
approach to the models, relationships, queries, and routes each time.
allows me to see where the advantages and disadvantages to each approach
pop-up. It is usually in this process where I end up answering the
of questions that you asked below.

My apologies if this seems a little elementary (and I did not explicitly
answer your questions,) but this is the approach I find useful with
tools. Hope this helps.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs