You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To match the behavior of HTML, id isn't required when using <form phx-submit="save"> ... so <LiveForm phx-submit="save">... should have similar behavior.
We shouldn't be injecting an id either. The client should allow the developer to opt-in with recovery.
The text was updated successfully, but these errors were encountered:
I think this can be accomplished by creating a FormModel that's local to the LiveForm element if an ID is not present. If an ID is provided, the form model would be held by the coordinator.
I want to aim for feature parity with HTML. Is there a reason why id would he required for SwiftUI? If not then I'd like to match HTML which works, but is less featureful, without id
Gotcha, I think we'll find ourselves with less WTFs later on if we match these primitive behaviors. I cannot highlight any one instance this would happen but its always the ones we don't anticipate
To match the behavior of HTML,
id
isn't required when using<form phx-submit="save"> ...
so<LiveForm phx-submit="save">...
should have similar behavior.We shouldn't be injecting an
id
either. The client should allow the developer to opt-in with recovery.The text was updated successfully, but these errors were encountered: