DRYML: Removing one field needs all fields specified?
Reported by Kieran P | February 27th, 2010 @ 05:20 AM
The example from the agility tutorial (http://cookbook.hobocentral.net/tutorials/agility#task_reordering), says that to remove the position field, you need to use
<extend tag="form" for="Task">
<old-form merge>
<field-list: fields="description, users"/>
</old-form>
</extend>
However, what if you have 10, 20, or 30 fields? You need to specify each one. IF one gets added, you have to make sure you remember to add it.
I propose a new key to field-list, except_fields
<extend tag="form" for="Task">
<old-form merge>
<field-list: except_fields="position"/>
</old-form>
</extend>
Seems much cleaner and easier to use... thoughts?
Comments and changes to this ticket
-
Bryan Larsen February 27th, 2010 @ 02:04 PM
- State changed from “new” to “invalid”
- Tag cleared.
The capability you describe exists, is called "skip" and is documented here: http://cookbook.hobocentral.net/api_tag_defs/field-list
This capability is used internally, so if you do utilize it you may have to add a couple of extra fields. For instance, it's used for https://hobo.lighthouseapp.com/projects/8324/tickets/495
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bryan Larsen