任何与视图中显示的内容相关的逻辑都应该委托给helper方法，因为模型中的方法严格用于处理数据。

以下是你可以做的:

# 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...

<%= link_to_thing("text", @thing) %>

虽然可能有一种方法，但我倾向于将这种逻辑排除在模型之外。我同意你不应该把它放在视图中(保持简洁)，但除非模型将url作为数据块返回给控制器，路由的东西应该在控制器中。

(编辑:忘了我之前的废话…)

可能在某些情况下你会去到模型或者其他url。但我真的不认为这属于模型，视图(或者模型)听起来更合适。

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 <modelname>sController (e.g. "UsersController" is the controller of the model "User").

如果您发现自己在一个视图中编写了大量令人讨厌的逻辑，请尝试将逻辑移到更合适的地方;请求和内部通信逻辑可能属于控制器，与数据相关的逻辑可能放在模型中(但不包括显示逻辑，包括链接标签等)，而纯粹与显示相关的逻辑将放在帮助器中。

你可能还会发现以下方法比包含所有方法更简洁:

class Thing
  delegate :url_helpers, to: 'Rails.application.routes' 

  def url
    url_helpers.thing_path(self)
  end
end

任何与视图中显示的内容相关的逻辑都应该委托给helper方法，因为模型中的方法严格用于处理数据。

以下是你可以做的:

# 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...

<%= link_to_thing("text", @thing) %>

我真的很喜欢清洁解决方案。

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

来自http://hawkins.io/2012/03/generating_urls_whenever_and_wherever_you_want/