We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maybe it would be clearer and cleaner if field name parameter is not named 'field' in schema.add_field usage example:
class MyModel(DynamicModel): name = models.CharField(max_length=100) # regular field schema.add_field(name='field', type='CharField')
I recommend something more descriptive like age to make usage more obvious.
schema.add_field(name='age', type='IntegerField')
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Maybe it would be clearer and cleaner if field name parameter is not named 'field' in schema.add_field usage example:
I recommend something more descriptive like age to make usage more obvious.
The text was updated successfully, but these errors were encountered: