feat: add migration metadata to observation schema #280
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This adds a new field, `migrationMetadata`, which has two sub-fields: - `originalDocument`: the original observation, in case we ever need it - `hypercore`: metadata about the observation in the old Hypercore I considered adding this to the `Common` schema, but I don't think it makes sense there because we won't necessarily be migrating all types, like `CoreOwnership`.
EvanHahn
force-pushed
the
migration-metadata
branch
from
aab0319 to
9e2b017
Compare
EvanHahn
changed the title
tomasciccola
approved these changes
Dec 18, 2024
EvanHahn
added a commit
to digidem/comapeo-core
that referenced
this pull request
Dec 19, 2024
This new version adds a new property to the Observation table, `migrationMetadata`. See [`@comapeo/schema` PR 280][0] for details. [0]: digidem/comapeo-schema#280
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a new field,
migrationMetadata, which has two sub-fields:originalDocument: the original observation, in case we ever need ithypercore: metadata about the observation in the old HypercoreI considered adding this to the
Commonschema, but I don't think it makes sense there because we won't necessarily be migrating all types, likeCoreOwnership.