On Feb 11, 2008, at 10:15 AM, Aaron Lehmann wrote:
Possibly instead of returning an error, it might resolve the name,
and take an optional callback that performs said resolution? That
way, people who have their own resolution code can easily factor it
in.
Or is this a case where
On Feb 11, 2008, at 10:06 AM, Christian Theune wrote:
Hi,
Aaron Lehmann schrieb:
Christian,
What if people are relying on those error messages to do different
things?
Possibly they already have normalization code they expect to come
into play in this situation, which is different than
Hi,
Aaron Lehmann schrieb:
Christian,
What if people are relying on those error messages to do different things?
Possibly they already have normalization code they expect to come into
play in this situation, which is different than yours
.
I see that people might be doing that, however, it
Christian,
What if people are relying on those error messages to do different
things?
Possibly they already have normalization code they expect to come into
play in this situation, which is different than yours
.
On the other hand, having to do this seems annoying, so as someone
writing
Hi,
Aaron Lehmann schrieb:
On Feb 11, 2008, at 10:15 AM, Aaron Lehmann wrote:
Possibly instead of returning an error, it might resolve the name, and
take an optional callback that performs said resolution? That way,
people who have their own resolution code can easily factor it in.
Or
Hi,
the standard name chooser makes sure that the character '+', '@' are not
used in the beginning of a name and '/' is never used.
When asking the name chooser to choose a name for me, I thought it would
normalize those characters away, giving me a usable name.
Reading the interface,
Aaron Lehmann schrieb:
On Feb 11, 2008, at 10:06 AM, Christian Theune wrote:
Hi,
Aaron Lehmann schrieb:
Christian,
What if people are relying on those error messages to do different
things?
Possibly they already have normalization code they expect to come
into play in this situation,
