I have repeatedly run into a bug where the field configurations I declare on an AshBackpex.LiveResource are incompatible with the specified create_action or update_action.
Most often this takes the form of adding a field which refers to a relationship, calculation or even attribute that is a valid field but that the configured action doesn't accept as an input.
While it should be possible to override this, the default behavior should be as follows:
- All accepted inputs for the
create_action appear in the :new form
- All accepted inputs for the
update_action appear in the :update form
- Any other fields appear only in the
:show and :index views by default.
I have repeatedly run into a bug where the field configurations I declare on an
AshBackpex.LiveResourceare incompatible with the specifiedcreate_actionorupdate_action.Most often this takes the form of adding a field which refers to a relationship, calculation or even attribute that is a valid field but that the configured action doesn't accept as an input.
While it should be possible to override this, the default behavior should be as follows:
create_actionappear in the:newformupdate_actionappear in the:updateform:showand:indexviews by default.