Jamie Matthews

We do use the Django Admin, but we only expose it to internal users (ie devs). We have a single boolean flag `is_superuser` which distinguishes users that can log into...

Concern about this is that it doesn't compose nicely. This won't work: ```python prepare, project = specs.process([ "title", {"publisher_id": pairs.related_field("publisher", "id")}, {"publisher_name": pairs.related_field("publisher", "name")}, ]) ``` You'd need to do...

See https://github.com/dabapps/django-readers/issues/58

Hi, I don't think this is going to be an easy fix, because the `ProjectionSerializer` doesn't know anything at all about what it's serializing. We might be able to silence...

Hi, Does `remove_query_param` do what you need? https://github.com/j4mie/django-spurl#remove_query_param

Aha, yes, sorry. Misunderstood. It doesn't look like this functionality is in urlobject. Is it worth adding, @zacharyvoase ? Otherwise, we could do something along the lines of: ``` url.set_query_param(key,...

I think I'd prefer to add this functionality to `remove_query_param`, by extending it to handle `foo=bar` as well as just `foo` as an argument, rather than adding `remove_query_param_value` (unless you...

Update: it turns out this was because the form's `action` attribute was empty (`""`). This generally seems to work in browsers but is technically a violation of the spec -...

> Was this the original configuration that you saw the exception in? If so, was that an oversight or was it intentional? Curious to know what `up-validate` would be submitting...

Sorry for the slow reply on this. I don't use `django-crispy-forms` myself so I don't know much about it, but from looking at the example I think you're right -...