Skip to content
New issue

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

django_tables2 2.0 #549

Merged
merged 18 commits into from
Apr 10, 2018
Merged

django_tables2 2.0 #549

merged 18 commits into from
Apr 10, 2018

Conversation

jieter
Copy link
Owner

@jieter jieter commented Mar 8, 2018

refs #526

We also need to do:

  • Make a 1.x branch for future fixes.
  • Proper upgrading docs/release notes.
  • Remove 'Upgrading from django-tables Version 1' from the docs. (added in 6d69f49 Aug 2, 2011)

@jieter jieter force-pushed the two branch 4 times, most recently from 3e4f064 to 1957f91 Compare March 16, 2018 10:55
@jieter jieter force-pushed the two branch 2 times, most recently from dbad7be to 4c9662b Compare March 26, 2018 08:05
jieter and others added 18 commits April 10, 2018 16:41
* Adjust "null" to expected behavior

Add "not" to ensure that when null is True (making ` None or '' ` distinct from False) that the default placeholder (--) is rendered
…name, or do nothing to it. fixes #491

Doing it this way conforms to the django recommendations:
https://docs.djangoproject.com/en/stable/topics/db/models/#verbose-field-names

> The convention is not to capitalize the first letter of the verbose_name.
> Django will automatically capitalize the first letter where it needs to.
@jieter jieter merged commit 8f424eb into master Apr 10, 2018
@jieter jieter deleted the two branch April 12, 2018 14:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants