Changes between Initial Version and Version 1 of Ticket #25347, comment 2


Ignore:
Timestamp:
Sep 8, 2015, 8:45:01 AM (9 years ago)
Author:
Tim Graham

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #25347, comment 2

    initial v1  
    11I'm not sure how that's required. This isn't a bug but rather a limitation that I'm hoping can be fixed as a new feature.
    22
    3 If you iterate over request.POST, I'm expecting that __getitem__ can handle giving me a list or a scalar depending on what was sent in the form data. Right now I have to know the actual key in order to extract the given key as a list so I don't end up with the last item in it.
     3If you iterate over `request.POST`, I'm expecting that `__getitem__` can handle giving me a list or a scalar depending on what was sent in the form data. Right now I have to know the actual key in order to extract the given key as a list so I don't end up with the last item in it.
    44
    5 The other alternative I have is to run getlist() on every single key and then iterate over scalars as if they are lists which just adds unneeded overhead. I guess I could also roll out my own request data parser to replace QueryDict, but it seems like this should be core functionality that QueryDict can get right itself.
     5The other alternative I have is to run `getlist()` on every single key and then iterate over scalars as if they are lists which just adds unneeded overhead. I guess I could also roll out my own request data parser to replace `QueryDict`, but it seems like this should be core functionality that `QueryDict` can get right itself.
Back to Top