Agreed. I can definitely see how this would be both unexpected and frustrating. I added a note to the data action for the next release along these lines:
If you wish to add new data fields, you may create them below. Just enter a comma separate list of single words. However, be VERY careful to not enter a BoltWire command ([[bolt:docs.handbook.commands|reserved words]]) or you may get unexpected behavior. To delete a field, delete its contents above. I'm still wondering if there isn't some way to distinguish between commands and data fields. But nothing comes to mind short of massive disruptions to existing sites. This is one of those cases where hindsight may be better than foresight. Like zones. On the other hand, most of us have managed to get along ok like this, and in fact I enjoy a simpler syntax. So maybe it is best to continue as we are. Open to suggestions of course. We can always add some kind of config setting to change core behavior! Cheers Dan On Tue, Oct 6, 2009 at 9:02 AM, Hans <[email protected]> wrote: > > Perhaps such an important form as adding Data fields could check if > the data field name entered is part of a list of 'special command > words' and will refuse the input with a warning message. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
