mugle-dev team mailing list archive

[Prageeth Silva <prageethsilva@xxxxxxxxx>]

Oh I just realised, earlier it was automatically handled by relationships in
the datastore.

I totally forgot these were changed to have keys in them. This means, we
have to have specific service methods.

OK, at the moment this seems more pressing and I'll get this implemented
ASAP.

If any of you don't mind please go ahead with implementing the error
messages. Also, I agree with using CSS to hide the message.


On Wed, May 18, 2011 at 10:48 PM, Jens Pfau <jens.pfau@xxxxxxxxx> wrote:

> Thanks for your answer. How do I remove an object from the datastore (in
> this case an achievement)?
>
>
> On Wed, May 18, 2011 at 10:11 PM, Matt Giuca <matt.giuca@xxxxxxxxx> wrote:
>
>>
>> As to editing names and descriptions. Developers are not allowed to change
>>> the "name" (referring to the unique URL name given for a game, user,
>>> devteam, etc).
>>> However, the users are allowed to change their Full Name, and similar
>>> rules apply for games and dev teams. This means, potentially the description
>>> can be empty as far as the
>>> backend if concerned. Come to think of it, I'm not quite sure if this is
>>> the best option, but for now, I think the checking for empty strings should
>>> be done on client no matter what.
>>>
>>
>> Well nothing will break if you have an empty full name or description. It
>> just will look weird. I don't mind either way if the UI (editor) enforces
>> rules like this; likewise for maximum lengths (just pick a reasonable
>> length). The backend won't enforce it, which means users *can* do strange
>> things if they really want to, but they aren't security problems.
>>
>
>


-- 
*Prageeth Silva*