The form - to create a new path or edit an existing one - is not properly backed by a changeset. I think this is an artifact from a previous data model prototype, and there is currently no reason for it to not use LiveDataAssign.changeset/2
The effect of this issue is that attempts to create or update Live Data with an invalid path will fail silently, without showing any error message to the user.
NOTE that this will require upstream changes from beacon, as the full changeset is not publicly exposed right now, only the path changeset.
The form - to create a new path or edit an existing one - is not properly backed by a changeset. I think this is an artifact from a previous data model prototype, and there is currently no reason for it to not use
LiveDataAssign.changeset/2The effect of this issue is that attempts to create or update Live Data with an invalid path will fail silently, without showing any error message to the user.
NOTE that this will require upstream changes from beacon, as the full changeset is not publicly exposed right now, only the path changeset.