Form might need more work - or I more instruction #503
-
It is no doubt the latter in case - but anyways I'm seeing
rendering
whereas I'd expect it to render something along the lines of
|
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 3 replies
-
is this a 'feature' issue more so than a 'bug' issue, @joeldrapper ? I mean -- is the intention with the FormWith adapter to emulate the Rails helper 1:1 ? |
Beta Was this translation helpful? Give feedback.
-
Hey @wdiechmann, the |
Beta Was this translation helpful? Give feedback.
-
The adapters are meant to be one-to-one mappings of the built-in Rails helpers. If they don't match the underlying adapters, that's a bug. There's no space for new features in the adapters because they map to defined things. Helper features should be pitched to Rails core. That said, I will be looking at creating a Phlex-based form abstraction in the next few months that will give us space to define our own features. |
Beta Was this translation helpful? Give feedback.
-
I am really struggling with this 😢 May have narrowed at least one of the issues to my lack of understanding how to implement this:
|
Beta Was this translation helpful? Give feedback.
-
with 'regular' forms it's not a big issue to write the resource yourself - like |
Beta Was this translation helpful? Give feedback.
-
dang - for a brief moment I really thought to have cracked it! Tried:
because I thought: hey perhaps I'm supposed to not use view_helpers (or am doing them wrong) The 'form' ( ..do |form| ) returns
|
Beta Was this translation helpful? Give feedback.
-
ok - I dug into the ruby API and as it stands TIL - using arguments with yield 😃 so sorry to have waisted so much valuable bandwidth on my total lack of command of Ruby 😢 |
Beta Was this translation helpful? Give feedback.
ok - I dug into the ruby API and as it stands
yield
has the ability to offer arguments....TIL - using arguments with yield 😃
so sorry to have waisted so much valuable bandwidth on my total lack of command of Ruby 😢