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
Find a way to change control file metadata [without snapshotting the file table].
metadata should be change controlled because the outcome can be stark e.g. in the csv app change the unique column from email to something-else
Context
LIXDK-152 added file metadata without capabilities to track changes in the metadata.
File metadata is necessary to establish an app <-> plugin communication. For example, the CSV app (will) leverage(s) the metadata field to set a unique column from the app by prompting the user "what's the unique column in this csv?". The csv plugin then leverages the unique column to track changes, merge, etc.
The text was updated successfully, but these errors were encountered:
A trivial (and therefore probably correct way) is to store snapshots of the metadata field in the Change table. Apps (and lix itself) can query the Change table for metadata changes.
Saved change schema
constchange={"id": "uuid","file_id": "file.id",// prefixed with lix for namespacing"type": "lix_file_metadata","value": file.metadata}
Proposal
Find a way to change control file metadata [without snapshotting the file table].
metadata should be change controlled because the outcome can be stark e.g. in the csv app change the unique column from
email
tosomething-else
Context
LIXDK-152 added file metadata without capabilities to track changes in the metadata.
File metadata is necessary to establish an app <-> plugin communication. For example, the CSV app (will) leverage(s) the metadata field to set a unique column from the app by prompting the user "what's the unique column in this csv?". The csv plugin then leverages the unique column to track changes, merge, etc.
The text was updated successfully, but these errors were encountered: