Giters
craigds
/
django-fieldsignals
Django signals for changed fields
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
112
Watchers:
8
Issues:
17
Forks:
10
craigds/django-fieldsignals Issues
README outdated for changed_fields key now being a string
Closed
3 years ago
RemovedInDjango40Warning
Closed
4 years ago
Change `changed_fields` keys to be field names rather than field objects
Closed
4 years ago
"django-fieldsignals signals must be connected after the app cache is ready. "
Closed
5 years ago
Comments count
1
Model.refresh_from_db() does not update _fieldsignals_originals
Updated
5 years ago
Comments count
1
GenericForeignKey problem
Updated
6 years ago
Getting the user who changed the field
Closed
6 years ago
Comments count
2
Admin conflict?
Updated
7 years ago
Comments count
3
Will it work against JSONField of django 1.11 ? (native postgres field)
Closed
7 years ago
Comments count
2
can we call it from listing page
Closed
7 years ago
Comments count
1
changed_fields with no changes.
Closed
7 years ago
django-fieldsignals signals must be connected after the app cache is ready
Closed
7 years ago
Comments count
5
Fieldsignals in Views
Closed
7 years ago
Comments count
1
AttributeError: 'OneToOneRel' object has no attribute 'value_from_object'
Closed
9 years ago
Comments count
2
get_fields() AppRegistryNotReady: Models aren't loaded yet.
Closed
9 years ago
Comments count
2
have a 'many to many' field in signal, go wrong
Closed
9 years ago
Comments count
12
connecting a fieldsignal breaks pickle-ability of models
Closed
13 years ago