G’day:
this is already solved
Should I therefore assume I am the first person to even attempt to create
a component using the .lucee extension?!?
No, of course not, i recognized that as well but it was not happening in
previous versions, because there was no Component.lucee, it also not
happening in every case.
MichaOn Thu, Apr 16, 2015 at 11:50 AM, Adam Cameron <@Adam_Cameron> wrote:
G’day:
From bitbucket:
syntax error in component.lucee
Adam Cameron https://bitbucket.org/da_cameron created an issue 22
minutes agoThe code in component.lucee is:
Obviously this needs to be:
<:component displayname=“Component” hint=“This is the Base Component”></:component>
Or, really, it should be:
component {
}(it should not be in tags, and it should not have pointless comments)
But once cannot make a .lucee component as it stands!
How are your tests passing, I wonder?
Should I therefore assume I am the first person to even attempt to create
a component using the .lucee extension?!?–
Adam–
You received this message because you are subscribed to the Google Groups
“Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/5e29fbec-efcd-419b-8947-89736eb453a4%40googlegroups.com
https://groups.google.com/d/msgid/lucee/5e29fbec-efcd-419b-8947-89736eb453a4%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
this is already solved
Cool! I’ve just hacked my own one in the mean time to move fwd.
Should I therefore assume I am the first person to even attempt to create
a component using the .lucee extension?!?
No, of course not, i recognized that as well but it was not happening in
previous versions, because there was no Component.lucee, it also not
happening in every case.
Righto.On Thursday, 16 April 2015 12:20:16 UTC+1, Micha wrote:
–
Adam