Revisions of #307

Contributors: Dennis Hackethal
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.

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.

Version 1 · #307 · Dennis Hackethal · 4 months ago · Criticism
1 comment: #309

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.parameter:↵
↵
So instead of↵
↵
```ruby↵
@helper_module.instance_method(@action_name).bind_call(view_context)↵
```↵
↵
I would do↵
↵
```ruby↵
@helper_module.send(@action_name, view_context)↵
```↵
↵
And the parameter list of each Hiccdown method would start accordingly:↵
↵
```ruby↵
module ProductsHelper↵
  def self.index vc #, …↵
    # …↵
  end↵
end↵
```

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

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

I would do

@helper_module.send(@action_name, view_context)

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

module ProductsHelper
  def self.index vc #, …
    # …
  end
end
Version 2 · #308 · Dennis Hackethal · 4 months ago · Criticism
1 comment: #311

 19 unchanged lines collapsed
vc.some_helper_method↵ end↵ ↵ def some_helper_method↵ # …
 3 unchanged lines collapsed
 19 unchanged lines collapsed
vc.some_helper_method

end

def somehelpermethod
# …

 3 unchanged lines collapsed
Version 3 · #310 · Dennis Hackethal · 4 months ago · Criticism