dryml parser should fail when param content replacement does not match anything
Reported by Betelgeuse | October 31st, 2009 @ 10:51 PM | in Beyond Hobo 1.0
<test-page>
<form:>
<test-form>
<field-list:>
<h2>field-list</h2>
</field-list:>
<foobar-param:>FOOBAR</foobar-param:>
<actions:>
<h2>actions</h2>
</actions:>
</test-form>
</form:>
</test-page>
Been having problems with customizing transaction forms and
stuff not matching. Any way
it would be helpful if at least in development made the dryml view
rendering would fail
when a parameter content replacement matches nothing. As far as I
know always when you
use <param:> you want the stuff to do something instead of
being silently ignored.
Comments and changes to this ticket
-
Betelgeuse November 1st, 2009 @ 09:45 AM
- Tag changed from dryml to dryml, usability
-
Bryan Larsen November 1st, 2009 @ 03:03 PM
- Tag changed from dryml, usability to dryml, enhancement, usability
So true, I've run into this many times.
-
Betelgeuse November 1st, 2009 @ 03:24 PM
- Tag changed from dryml, enhancement, usability to dryml, enhancement, error-messages, usability
Looking at the dryml list again maybe this is a duplicate of #110? Any way this is more descriptive so could make sense to mark that one as a duplicate of this one.
-
Tom Locke November 17th, 2009 @ 04:03 PM
- State changed from new to open
- Milestone set to Beyond Hobo 1.0
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 your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
People watching this ticket
Referenced by
- 522 dryml parser should fail when trying to use default content but the tag doesn't support it I think fixing #521 will also fix this one. However, I'll...
- 110 A call to <foo:> should be an error Described better in #521