Sorry about that @joc - I didn’t consider other clients aside from the command line tool and snapd-glib. Both these clients handle any fields missing and have default values. @chipaca - do you think that’s a reasonable assumption? I can update the REST docs if that’s the case.
@joc - which fields are causing the issue for you? Is it hard to update your tools?
What would be the best way to communicate a change like this? On this forum?
There’s one change that I think is very important - making the install-date optional. This is because it gets sent as 0001-01-01T00:00:00Z if unset, which is (technically) a valid date.
This structure is used for both snaps returned from /v2/find and /v2/snaps - many of the fields only make sense in one of those. So omitting them makes it much easier to understand.
The remaining fields are just unlikely to be set and make the output noisy.