Saving, Saved or Failed
Series · Entities front-endEvery form in the app shows saving, saved or failed the same way, instead of each one re-inventing it. One small object carries the state, and one panel shows it.
Patterns, gotchas and small wins from fifteen-odd years of .NET and web work — the Regira packages and modules, entity pipelines, editorial front-ends and everything between.
Every form in the app shows saving, saved or failed the same way, instead of each one re-inventing it. One small object carries the state, and one panel shows it.
Show the flat list an API returns as a tree users can expand, select and drag to a new parent. No recursive component, and illegal drops are refused in the browser before they reach the server.
Edit forms where Cancel always works, a save shows what the server stored, a refused delete says so, and a deleted record can be brought back. Four decisions, in Vue.
A list screen users can bookmark, share and hit Back on without losing their filters, and that never shows an error over data that loaded fine. The rules behind it, and the Vue composables that apply them.