compatible with django_model_utils Choices

[philipn]

compatible with django_model_utils Choices

[rpkilby]

Hi @dbinetti. Looking over the code, the choices field is just a regular CharField that pulls its choices from the parent model, so it would exhibit the same characteristics as the underlying field.

What are you're trying to accomplish by using the human-readable value instead of the code value? Could you provide a concrete example?

Using the human-readable value is generally problematic, as this is a display value subject to transformation (language translation, capitalization, etc...). The code values are more durable since they aren't transformed.

[dbinetti]

I'm trying to make the URL human readable (and fungible directly). However, your point about transformation makes good sense. I'll let this go.

[rpkilby]

I'd say your best bet is to use code values that are human friendly.

eg,

# Use:
STATUSES = (
    ('started', 'Started'),
    ('in_progress', 'In Progress'),
    ('finished', 'Finished'),
    ('errored', 'Errored'),
)

# instead of
STATUSES = (
    ('s', 'Started'),
    ('p', 'In Progress'),
    ('f', 'Finished'),
    ('e', 'Errored'),
)

[dbinetti]

actually, i'm using integers (order is important) motel_utils allow for a
three-tuple (1,'foo', 'Foo Bar'), so that would potentially work, but i
think i'll just work things on the front end appropriately.

tks

On Wed, Mar 16, 2016 at 1:43 PM, Ryan P Kilby [email protected]
wrote:

I'd say your best bet is to use code values that are human friendly.

eg,

Use:STATUSES = (

('started', 'Started'),
('in_progress', 'In Progress'),
('finished', 'Finished'),
('errored', 'Errored'),

)

instead ofSTATUSES = (

('s', 'Started'),
('p', 'In Progress'),
('f', 'Finished'),
('e', 'Errored'),

)

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#78 (comment)