This issue is a little bit hard to describe... in some cases, the admin calls a module's add or edit function within a context, which pre-fills some bones e.g. a RelationalBone with mybone.dest.key=somekey and should validate them.
Depending on the skeleton, this might already lead in a creation or edit of the entry on initial load.
For this, there should be a special bounce-flag, which does the same as bounce=true, but without error reporting. So the input is parsed into the skeleton and returned as far as possible, but there should be no error reporting, this is done when "Save" is being hit.
Proposal:
bounce=true should do the same as now, parse data, report errors, but don't save.
bounce=silent should do the same as bounce=true, but without returning errors.
This issue is a little bit hard to describe... in some cases, the admin calls a module's add or edit function within a context, which pre-fills some bones e.g. a RelationalBone with
mybone.dest.key=somekeyand should validate them.Depending on the skeleton, this might already lead in a creation or edit of the entry on initial load.
For this, there should be a special bounce-flag, which does the same as bounce=true, but without error reporting. So the input is parsed into the skeleton and returned as far as possible, but there should be no error reporting, this is done when "Save" is being hit.
Proposal:
bounce=trueshould do the same as now, parse data, report errors, but don't save.bounce=silentshould do the same asbounce=true, but without returning errors.