So Aurelien and Florian, what do you think? Should we use the hex
representation of the UUID and should I keep backward compatibility.
If we can't see any valid reason for converting to ints today, I would
personally vote for not converting in the REST API, and for mailman.client
to return
Hi Florian!
I think mailmanclient should not expose a different value as the REST
API does (the fact that it's an int representation of a uuid isn't
exactly obvious from the outside, so a non-explicit conversion could
potentially lead to some confusion).
Hmm, to me the current situation is
If the user_id value changes depending on whether
you are using the API directly via HTTP or through mailmanclient, that
might be hard to understand.
Ah, very good point. I'll do the conversion myself then I guess.
A.
___
Mailman-Developers mailing
Hey folks,
Mailman stores user_ids as UUIDs in the database, and they are converted on
the fly to integers by the REST API.
However, the mailmanclient library do not convert them back to UUID. Do you
think this is something that it should do, or should I handle this
conversion in my own code?
