Opened 17 years ago
Closed 17 years ago
#7406 closed (wontfix)
Json widget for newforms
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Forms | Version: | dev |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Someday/Maybe | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
I've added a widget for newforms for handling Json data – it uses a text field that has a JSON string like {“a”:”b”, “c”:”d”} it displays it in a series of form inputs for every key-value. When saving data two lists are dumped into a dict and then into a JSON.
Attachments (2)
Change History (6)
by , 17 years ago
Attachment: | json_inputs.patch added |
---|
comment:2 by , 17 years ago
I suspect that since this is a new widget, rather specialized (a form widget that creates JSON specially and directly from the form submission, instead of a separate post form data processing activity), and does not require inclusion in Django to work correctly, that it should be hosted externally until such impetus from the community makes it work including internally.
However, I'm not a core dev, so I can't make the final decision, but at best I see this as Someday/Maybe.
comment:3 by , 17 years ago
Triage Stage: | Unreviewed → Someday/Maybe |
---|
gav is right, this widget is too specific do justify inclusion in Django itself. Please post this to djangosnippets.
Marking as Someday/Maybe to ease ticket triaging for core devs.
comment:4 by , 17 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
This is a pretty specific widget, for a fairly edge case requirement. It would be hard to argue that there is a widespread need for this capability. As gav and mrts noted, this is much better suited to djangosnippets, or a 3rd party widget library.
The patch