is this possible/good-practice to have one controller attached to many
in REST…something like
work:
has_many :tasks
home:
has_many :tasks
personal:
has_many :tasks
and then store work_id or home_id, or personal_id in tasks table.
is this possible/good-practice to have one controller attached to many
in REST…something like
work:
has_many :tasks
home:
has_many :tasks
personal:
has_many :tasks
and then store work_id or home_id, or personal_id in tasks table.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs