chore: fix null metadata and annotation json representation #3177
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.
Overview
In the DB instead of a NULL field value we end up having a 'null'::jsonb string, which is a pain to handle when it comes to data migrations, as we need to do something like this:
Unfortunately ent has a long known issue around value scanners in mixins: ent/ent#3785
This patch depends on ent/ent#4421 being merged, right now it is just pointed to my fork for testing purposes.
Once it is deployed, I will create a new PR with the migrations to correct the existing data.