Validation
Validate configuration versus Validate everything, the four finding categories, and the promise that every actionable finding carries a remedy.
Two buttons, two questions#
| Button | Answers |
|---|---|
| Validate configuration | Options, limits, security, migration declarations, provider readiness, asset metadata. Fast, and independent of your project's files. |
| Validate everything | All of the above plus the package's own files, the project's resolved dependencies, the platform, the identity scan, and a real write/read/delete through the framework's storage. |
Reach them from NexusForge → Persistence → Validate Configuration or Validate Everything, or from the Validation page inside the window.
Four categories, and only two are problems#
| Category | Meaning |
|---|---|
| ERROR | Something is wrong and will not work as configured. |
| WARNING | Something to decide about. It will run, and you should know what it costs. |
| INFO | Worth knowing. Nothing to fix. |
| NOT VERIFIED | Nothing was run for this combination. Not a failure, and not a promise. |
Every actionable finding carries three things#
What is wrong, why it matters, and how to fix it. That structure is enforced by a structural test on PersistenceValidationCatalog, so a finding cannot ship without a remedy.
WARNING Cloud is enabled but no provider is installed.
Why: Cloud support requires an installed provider/adapter; the package ships no service, account or credential.
Fix: Implement ICloudTransport for your service, wrap it in TransportCloudSaveProvider, and pass both to
CloudSaveSyncService.The storage probe#
Test local storage writes 512 bytes into the probe's own _probe directory, reads them back through the same verified path a save uses, deletes them and reports what happened — including which promotion strategy the platform reported. It never touches a slot, and it cleans up after itself.
Next#
- Diagnostics — the runtime side of the same finding format.
- Platform support — what "verified" means per environment.
- Troubleshooting — symptoms in the order people meet them.
Something wrong on this page? Every page here describes behaviour that is checked in the repository. If a page and the package disagree, the package wins.
Report a documentation problem · Frequently asked questions · Troubleshooting