Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
TODO: Docs: Document usage of USE_NATIVE_JSONFIELD
See original GitHub issueWith #1173 landing, we should recommend using USE_NATIVE_JSONFIELD, or possibly even defaulting to it (though defaulting may break backwards-compat for people upgrading).
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Use JSDoc: @todo
The @todo tag allows you to document tasks to be completed for some part of your code. You can use the @todo tag...
Read more >Google Docs: Online Document Editor | Google Workspace
Use Google Docs to create, and collaborate on online documents. Edit together with secure sharing in real-time and from any device.
Read more >Assign tasks from Google Docs - Android - Google Support
Open a document with assigned tasks in the Google Docs app. · Tap Edit Edit . · Find an assigned checklist item. ·...
Read more >2 Ways to Create a To Do List in Google Docs
A simple way to add a to do list within a Google Doc is to use a table. Tables are great ways to...
Read more >Google Apps Script quickstart | Google Docs
Google Workspace quickstarts use the API client libraries to handle some ... @see https://developers.google.com/docs/api/reference/rest/v1/documents/get
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m wondering if maybe removing the default False, so new users are forced to choose a value of
USE_NATIVE_JSONFIELDwould be a good idea? Along with a useful hint in a check - eg something like:“You must set a value of USE_NATIVE_JSONFIELD. Existing installs of dj-stripe that haven’t set this value, or those using Django<3.1 and not using postgres must use USE_NATIVE_JSONFIELD=False. New installs with postgres or with Django>=3.1 should prefer USE_NATIVE_JSONFIELD=True”
Then maybe in a future version (eg 3.0?) changing the default to True?
Thoughts @kavdev ?
I do have a production non native jsonfield, and I have been intending to upgrade, so I’ll do this in the next few days and prepare a migration guide for it.