feat: added metadata column to files #170
Merged
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.
Fixes #134 and #160
This basically introduces a new column
metadata
to thefiles
table of typejsonb
. The user can populate this with any data it wants by adding ametadata
object to themetadata[]
field in the multipart-form (metadata
field when updating files). For instance:In addition, we are moving away from the graphql client
github.com/hasura/go-graphql-client
togithub.com/Yamashou/gqlgenc
as I was running into some troubles dealing with jsonb objects. This has the side-effect the graphql code is much cleaner and easier to understand (this was long overdue to be honest).