Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / craigds/django-fieldsignals issues and pull requests
#25 - Add a trigger_on_create kwarg
Pull Request -
State: closed - Opened by craigds over 2 years ago
- 3 comments
#24 - README outdated for changed_fields key now being a string
Issue -
State: closed - Opened by nshafer almost 3 years ago
#23 - removed "=None"
Pull Request -
State: closed - Opened by guettli almost 4 years ago
#22 - RemovedInDjango40Warning
Issue -
State: closed - Opened by guettli almost 4 years ago
#21 - Py3 Syntax in README fixed.
Pull Request -
State: closed - Opened by guettli almost 4 years ago
#20 - Change `changed_fields` keys to be field names rather than field objects
Issue -
State: closed - Opened by craigds almost 5 years ago
#19 - django.utils.six is removed in latest Django
Pull Request -
State: closed - Opened by dedayoa about 5 years ago
- 3 comments
#18 - "django-fieldsignals signals must be connected after the app cache is ready. "
Issue -
State: closed - Opened by barbouche over 5 years ago
- 1 comment
#17 - Model.refresh_from_db() does not update _fieldsignals_originals
Issue -
State: open - Opened by ajhodges over 5 years ago
- 1 comment
#16 - GenericForeignKey problem
Issue -
State: open - Opened by ulladimil about 6 years ago
#15 - Getting the user who changed the field
Issue -
State: closed - Opened by veeral-patel over 6 years ago
- 2 comments
#14 - fixes #13
Pull Request -
State: closed - Opened by ScottEAdams almost 7 years ago
#13 - Admin conflict?
Issue -
State: open - Opened by ScottEAdams almost 7 years ago
- 3 comments
#12 - Add Python 3.6 and Django 2.0.X to the test suite.
Pull Request -
State: closed - Opened by tveastman almost 7 years ago
#11 - Will it work against JSONField of django 1.11 ? (native postgres field)
Issue -
State: closed - Opened by dmitry-saritasa over 7 years ago
- 2 comments
#10 - can we call it from listing page
Issue -
State: closed - Opened by pawanvirsingh over 7 years ago
- 1 comment
#9 - changed_fields with no changes.
Issue -
State: closed - Opened by invious over 7 years ago
#8 - django-fieldsignals signals must be connected after the app cache is ready
Issue -
State: closed - Opened by invious over 7 years ago
- 5 comments
#7 - Fieldsignals in Views
Issue -
State: closed - Opened by invious over 7 years ago
- 1 comment
#6 - fix AppConfig ready condition
Pull Request -
State: closed - Opened by PetrDlouhy almost 9 years ago
#5 - AttributeError: 'OneToOneRel' object has no attribute 'value_from_object'
Issue -
State: closed - Opened by ScottEAdams about 9 years ago
- 2 comments
#4 - get_fields() AppRegistryNotReady: Models aren't loaded yet.
Issue -
State: closed - Opened by ScottEAdams about 9 years ago
- 2 comments
#3 - have a 'many to many' field in signal, go wrong
Issue -
State: closed - Opened by Thomas-23 over 9 years ago
- 12 comments
#2 - Django fieldsignals installable with pip
Pull Request -
State: closed - Opened by PetrDlouhy almost 11 years ago
#1 - connecting a fieldsignal breaks pickle-ability of models
Issue -
State: closed - Opened by craigds almost 13 years ago