Alias api json field types.

[jortel]

The types defined in the model package for JSON fields should be aliased by the api package instead of being redefined (cut-n-paste). This will ensure they are consistent and that JSON fields can be migrated.

Note: This will likely cause openAPI generation issues/complexity. May not be worth it :-/

[RipulHandoo]

Hey @jortel
As i am looking forward to work on this issue.
I find myself stuck as i found the JSON type in model package like this.
However, I couldn't find any reference to this type in the api package. Could you please provide some guidance or clarification on how to handle the JSON type in the api package?
TLA!

[jortel]

Hey @RipulHandoo
The JSON type defined in the model package is not (cannot be) used and a leftover from before the migration package was introduced.
This issue has been moved back to the BACKLOG (from READY) for now. We need to put some more thought into this. As you can imagine, we're extremely cautious about changes to the model and REST resources at a core level.