Hiccdown Development Notes

Showing only those parts of the discussion that lead to #305 and its comments.

See full discussion·See most recent related ideas

Log in or sign up to participate in this discussion.

With an account, you can revise, criticize, and comment on ideas.

Discussions can branch out indefinitely. Zoom out for the bird’s-eye view.

Dennis HackethalOP·#1980

2nd of 2 versions leading to #305 (2 total)

Hiccdown methods should live in Rails helpers as class methods. That way, the problem described in #302 is solved – methods can be referenced unambiguously:

1
2
ruby
ProductsHelper.index
StoresHelper.index

CriticismCriticized2*

Dennis HackethalOP·#305

2nd of 2 versions

Does that mean they wouldn’t have access to the view_context? If so, calling helper methods from inside these class methods wouldn’t be possible.

Criticism of #1980Criticized1

Dennis HackethalOP·#310

3rd of 3 versions

If so, there might be a way to bind them to the view_context. Or I could definitely pass the view_context explicitly as the first parameter:

So instead of

1
ruby
@helper_module.instance_method(@action_name).bind_call(view_context)

I would do

1
ruby
@helper_module.send(@action_name, view_context)

And the parameter list of each Hiccdown method would start accordingly:

1
2
3
4
5
6
7
8
9
ruby
module ProductsHelper
  def self.index vc #, …
    vc.some_helper_method
  end

  def some_helper_method
    # …
  end
end

Criticism of #305