Multiple function attributes with colon question

dev support
1

Can someone explain why this:

component tc:schema="4.3" tc:route="/members" {}
and
property name="entity" tc:inject="tc.module.entity" tc:alias="membership";

is fine

but
public struct function newMembers() tc:route="/members/new" tc:verb="GET,POST" {}

throws the error

you can’t use the same attribute [tc] twice; Failed at …

Why can I use attributes with colons in everything but functions?

( I know this might have been discussed before years ago as there is also a note in the taffy docs about colons in atttributes, but I wasn’t part of that conversation)

2

there’s some background here

basically in cfscript : and = have similar meanings i.e. assignment, tags are a different kettle of fish

a-z and _ are permitted

3

it is ironic I can do one, but not two. (broken implementation)

The error seems inconsistent with how first key/value pair(s) is being eventually parsed into a value/key pair.

The truple here (if colon is same as equals, which is not) should inform the engine that it is a key pair with a colon key pattern (as you cant do dynamic assignment on an attribute from what i understand) and with no space before and after the colon it should not be treated as two params. (as Aaron suggested)

I find tc:route="/membership" is treated in validation same as tc:verbs="GET,POST" , (aka is being treated as tc=route=membership and tc=verbs='GET,POST') for validation, but not for variable declaration…

Does that assign membership to route,? and that object to tc? (nope) it does what you would expect, treats first one a tc:route key with value of membership… something is broken.

1st parm treated as two different things at the same time, so it’s NOT being used to assign route to tc, and throws an error because in valiation it is, so either way its unintentional broken implementation.

I dont agree that using colon is same as equals without braces in attributes, it’s bad syntax imho, colons outside of an object are not equality symbols (as brad and others pointed out), thats confusing to me (and others).

What does CF2025 support out of interest? I know it used to, but I think the optional brace thing probably caused this issue.

I’m not sure how the majority in that conversation wanted it fixed, but it wasn’t (guessing the ‘railo triage system’ was at work)

4

ACF also doesn’t support it