Can Rails Routing Helpers i e mymodel path model be Used in Models

Question

Say I have a Rails Model called Thing  Thing has a url attribute that can optionally be set to a URL somewhere on the Internet  In view code  I need logic that does the following    lt   if thing url blank    gt   lt    link to  Text   thing path thing     gt   lt   else   gt   lt    link to  Text   thing url    gt   lt   end   gt    This conditional logic in the view is ugly  Of course  I could build a helper function  which would change the view to this    lt    thing link  Text   thing    gt    That solves the verbosity problem  but I would really prefer having the functionality in the model itself  In which case  the view code would be    lt    link to  Text   thing link    gt    This  obviously  would require a link method on the model  Here s what it would need to contain   def link    self url blank     thing path self    self url end   To the point of the question  thing path   is an undefined method inside Model code  I m assuming it s possible to  pull in  some helper methods into the model  but how  And is there a real reason that routing only operates at the controller and view layers of the app  I can think of lots of cases where model code may need to deal with URLs  integrating with external systems  etc

User · Answer

In Rails 3  4  and 5 you can use   Rails application routes url helpers   e g   Rails application routes url helpers posts path Rails application routes url helpers posts url  host   gt   example com

User · Answer

While there might be a way I would tend to keep that kind of logic out of the Model  I agree that you shouldn t put that in the view  keep it skinny  but unless the model is returning a url as a piece of data to the controller  the routing stuff should be in the controller

User · Answer

I ve found the answer regarding how to do this myself  Inside the model code  just put   For Rails  lt   2   include ActionController  UrlWriter   For Rails 3   include Rails application routes url helpers   This magically makes thing path self  return the URL for the current thing  or other model path self association to other model  return some other URL

User · Answer

Edit  Forget my previous babble      Ok  there might be situations where you would go either to the model or to some other url    But I don t really think this belongs in the model  the view  or maybe the model  sounds more apropriate   About the routes  as far as I know the routes is for the actions in controllers  wich usually  magically  uses a view   not directly to views  The controller should handle all requests  the view should present the results and the model should handle the data and serve it to the view or controller  I ve heard a lot of people here talking about routes to models  to the point I m allmost starting to beleave it   but as I understand it  routes goes to controllers  Of course a lot of controllers are controllers for one model and is often called  lt modelname gt sController  e g   UsersController  is the controller of the model  User      If you find yourself writing nasty amounts of logic in a view  try to move the logic somewhere more appropriate  request and internal communication logic probably belongs in the controller  data related logic may be placed in the model  but not display logic  which includes link tags etc   and logic that is purely display related would be placed in a helper

User · Answer

I really like following clean solution   class Router   include Rails application routes url helpers    def self default url options     ActionMailer  Base default url options   end end  router   Router new router posts url    http   localhost 3000 posts router posts path    posts   It s from http   hawkins io 2012 03 generating urls whenever and wherever you want

User · Answer

I really like following clean solution   class Router   include Rails application routes url helpers    def self default url options     ActionMailer  Base default url options   end end  router   Router new router posts url    http   localhost 3000 posts router posts path    posts   It s from http   hawkins io 2012 03 generating urls whenever and wherever you want

User · Answer

Edit  Forget my previous babble      Ok  there might be situations where you would go either to the model or to some other url    But I don t really think this belongs in the model  the view  or maybe the model  sounds more apropriate   About the routes  as far as I know the routes is for the actions in controllers  wich usually  magically  uses a view   not directly to views  The controller should handle all requests  the view should present the results and the model should handle the data and serve it to the view or controller  I ve heard a lot of people here talking about routes to models  to the point I m allmost starting to beleave it   but as I understand it  routes goes to controllers  Of course a lot of controllers are controllers for one model and is often called  lt modelname gt sController  e g   UsersController  is the controller of the model  User      If you find yourself writing nasty amounts of logic in a view  try to move the logic somewhere more appropriate  request and internal communication logic probably belongs in the controller  data related logic may be placed in the model  but not display logic  which includes link tags etc   and logic that is purely display related would be placed in a helper

User · Answer

While there might be a way I would tend to keep that kind of logic out of the Model  I agree that you shouldn t put that in the view  keep it skinny  but unless the model is returning a url as a piece of data to the controller  the routing stuff should be in the controller

User · Answer

In Rails 3  4  and 5 you can use   Rails application routes url helpers   e g   Rails application routes url helpers posts path Rails application routes url helpers posts url  host   gt   example com

User · Answer

While there might be a way I would tend to keep that kind of logic out of the Model  I agree that you shouldn t put that in the view  keep it skinny  but unless the model is returning a url as a piece of data to the controller  the routing stuff should be in the controller

User · Answer

Any logic having to do with what is displayed in the view should be delegated to a helper method  as methods in the model are strictly for handling data   Here is what you could do     In the helper     def link to thing text  thing     thing url     link to text  thing path thing     link to text  thing url  end    In the view      lt    link to thing  text    thing    gt

User · Answer

I ve found the answer regarding how to do this myself  Inside the model code  just put   For Rails  lt   2   include ActionController  UrlWriter   For Rails 3   include Rails application routes url helpers   This magically makes thing path self  return the URL for the current thing  or other model path self association to other model  return some other URL

User · Answer

Edit  Forget my previous babble      Ok  there might be situations where you would go either to the model or to some other url    But I don t really think this belongs in the model  the view  or maybe the model  sounds more apropriate   About the routes  as far as I know the routes is for the actions in controllers  wich usually  magically  uses a view   not directly to views  The controller should handle all requests  the view should present the results and the model should handle the data and serve it to the view or controller  I ve heard a lot of people here talking about routes to models  to the point I m allmost starting to beleave it   but as I understand it  routes goes to controllers  Of course a lot of controllers are controllers for one model and is often called  lt modelname gt sController  e g   UsersController  is the controller of the model  User      If you find yourself writing nasty amounts of logic in a view  try to move the logic somewhere more appropriate  request and internal communication logic probably belongs in the controller  data related logic may be placed in the model  but not display logic  which includes link tags etc   and logic that is purely display related would be placed in a helper

User · Answer

Edit  Forget my previous babble      Ok  there might be situations where you would go either to the model or to some other url    But I don t really think this belongs in the model  the view  or maybe the model  sounds more apropriate   About the routes  as far as I know the routes is for the actions in controllers  wich usually  magically  uses a view   not directly to views  The controller should handle all requests  the view should present the results and the model should handle the data and serve it to the view or controller  I ve heard a lot of people here talking about routes to models  to the point I m allmost starting to beleave it   but as I understand it  routes goes to controllers  Of course a lot of controllers are controllers for one model and is often called  lt modelname gt sController  e g   UsersController  is the controller of the model  User      If you find yourself writing nasty amounts of logic in a view  try to move the logic somewhere more appropriate  request and internal communication logic probably belongs in the controller  data related logic may be placed in the model  but not display logic  which includes link tags etc   and logic that is purely display related would be placed in a helper

User · Answer

Any logic having to do with what is displayed in the view should be delegated to a helper method  as methods in the model are strictly for handling data   Here is what you could do     In the helper     def link to thing text  thing     thing url     link to text  thing path thing     link to text  thing url  end    In the view      lt    link to thing  text    thing    gt

User · Answer

You may also find the following approach cleaner than including every method   class Thing   delegate  url helpers  to   Rails application routes      def url     url helpers thing path self    end end

User · Answer

You may also find the following approach cleaner than including every method   class Thing   delegate  url helpers  to   Rails application routes      def url     url helpers thing path self    end end

User · Answer

I ve found the answer regarding how to do this myself  Inside the model code  just put   For Rails  lt   2   include ActionController  UrlWriter   For Rails 3   include Rails application routes url helpers   This magically makes thing path self  return the URL for the current thing  or other model path self association to other model  return some other URL

User · Answer

I ve found the answer regarding how to do this myself  Inside the model code  just put   For Rails  lt   2   include ActionController  UrlWriter   For Rails 3   include Rails application routes url helpers   This magically makes thing path self  return the URL for the current thing  or other model path self association to other model  return some other URL

User · Answer

Any logic having to do with what is displayed in the view should be delegated to a helper method  as methods in the model are strictly for handling data   Here is what you could do     In the helper     def link to thing text  thing     thing url     link to text  thing path thing     link to text  thing url  end    In the view      lt    link to thing  text    thing    gt

User · Answer

Any logic having to do with what is displayed in the view should be delegated to a helper method  as methods in the model are strictly for handling data   Here is what you could do     In the helper     def link to thing text  thing     thing url     link to text  thing path thing     link to text  thing url  end    In the view      lt    link to thing  text    thing    gt

User · Answer

While there might be a way I would tend to keep that kind of logic out of the Model  I agree that you shouldn t put that in the view  keep it skinny  but unless the model is returning a url as a piece of data to the controller  the routing stuff should be in the controller

[ruby-on-rails] Can Rails Routing Helpers (i.e. mymodel_path(model)) be Used in Models?

Examples related to ruby-on-rails

Examples related to rails-routing

Examples related to helpermethods