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
{{ message }}
This repository has been archived by the owner on May 6, 2020. It is now read-only.
Instead of JSONField consider doing a parent/child model to handle proc type information. (and other nested information). Autoscales model with Autoscale for web and worker records. This will only work in some cases. Might not map to health checks very well given it is a very nested structure.
There are two reasons why I want to see some exploration on this
Do validations outside of the JSON Schema hack and rather utilise built-in validations from Django / DRF or at least function based validations
If swagger (Specify the API using swagger #811) happens (or any auto-generated schema format) then having data concretely described it going to help a lot
This may not be viable at all, or is only viable when dealing with very simple structures, at best when we know it needs to only map down to the level of process type
The text was updated successfully, but these errors were encountered:
Instead of JSONField consider doing a parent/child model to handle proc type information. (and other nested information). Autoscales model with Autoscale for web and worker records. This will only work in some cases. Might not map to health checks very well given it is a very nested structure.
There are two reasons why I want to see some exploration on this
This may not be viable at all, or is only viable when dealing with very simple structures, at best when we know it needs to only map down to the level of process type
The text was updated successfully, but these errors were encountered: