Grace
Grace
I suppose this would make sense, especially if we want to support the addition of data models by other parties. But I worry about violating WYSIWYG.
I've done some investigations and am going to post some tickets regarding alignment with the JSON Table Schema and general simplification of the model files with a new label "refactor:json-table".
I think it's also worth keeping the `default` attribute.
Yeah, I got `precision` and `scale` confused, obviously. What terrible names. Anyway, I think you're right that we shouldn't co-opt `maxLength` for this purpose and instead should use separate attributes.
I support the addition of tags or labels. I agree no attempt should be made to specify the semantics. In other words, it should be entirely up to the data...
The addition of the "tags" attribute can be included with the json-table-schema refactor work. I suggest a `tag1=val1; tag2=val2` format.
Yeah, I've got that version running in my Circle CI instances using the below `circle.yml` sections (found the previous ticket). Unfortunately, I'm still running into the same problem. I think...
I'm getting the same problem even after removing docker from `machine.services`. Can you reproduce on a Circle CI instance where you believe it should work? The steps are simple, `docker...
I guess its this line now: https://github.com/chrisglass/django_polymorphic/blob/master/polymorphic/polymorphic_model.py#L180 Any reason why you chose to do this? Any interest in finding a way around it (maybe metaclasses like Django itself uses)?