You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As some new UI work for workspaces and settings is in-flight, it would be nice to offer some additional information about stuff stored on disk. The only thing that really jumps out at me (without adding a bunch of stuff like history/rollback), is the file-system level information, namely modified and created time. This would enable the UI to answer use cases like "find the settings i most recently changed " or "find the workspace I was working on last Tuesday"
It looks like a workspace already has a metadata field (id lives there), so adding a last_modified and created would be reasonable, presumably as ISO 8061 dates.
I guess these would be overwritten on import/export, with the on-disk time always winning.
The settings API response looks a little more complicated, and perhaps these could just be added to the top level of each member of the settings array.
... or metadata could be added, with these in it, and eventually extended... though the buck has to stop somewhere, and I don't imagine much but sadness if settings carried anything not validated by the schema, or how it would get populated... HTTP headers?
Of course, open to any other suggestions of what might be hidden in there that would help folks navigate this stuff!
The text was updated successfully, but these errors were encountered:
As some new UI work for workspaces and settings is in-flight, it would be nice to offer some additional information about stuff stored on disk. The only thing that really jumps out at me (without adding a bunch of stuff like history/rollback), is the file-system level information, namely modified and created time. This would enable the UI to answer use cases like "find the settings i most recently changed " or "find the workspace I was working on last Tuesday"
It looks like a
workspace
already has a metadata field (id
lives there), so adding alast_modified
andcreated
would be reasonable, presumably as ISO 8061 dates.I guess these would be overwritten on import/export, with the on-disk time always winning.
The settings API response looks a little more complicated, and perhaps these could just be added to the top level of each member of the
settings
array.... or
metadata
could be added, with these in it, and eventually extended... though the buck has to stop somewhere, and I don't imagine much but sadness if settings carried anything not validated by the schema, or how it would get populated... HTTP headers?Of course, open to any other suggestions of what might be hidden in there that would help folks navigate this stuff!
The text was updated successfully, but these errors were encountered: