Rework the Token parsing to allow for namespacing and options passing directly. #6

New Issue

mcndave · 2023-02-02T13:51:22Z

mcndave commented

2023-02-02 13:51:22 +00:00

Options can be passed through tokens, but it is not handled as it should.
ui.form.post must be written this way, and no other option can be passed.

This task would allow tokens to now allow such statements :

ui:form.post.no-csrf.no-enctype, ui:form.no-enctype.no-csrf.post, ui:form.no-csrf.no-enctype.post, etc.. to all be forward to a single token, being in this case "ui:form" (notice the new facultative namespacing occuring here)

Options can be passed through tokens, but it is not handled as it should. ui.form.post must be written this way, and no other option can be passed. This task would allow tokens to now allow such statements : `ui:form.post.no-csrf.no-enctype`, `ui:form.no-enctype.no-csrf.post`, `ui:form.no-csrf.no-enctype.post`, etc.. to all be forward to a single token, being in this case "ui:form" (notice the new facultative namespacing occuring here)

mcndave added the

enhancement

2.0 features

labels 2023-02-02 13:51:22 +00:00

mcndave added this to the Kanban project 2023-02-02 13:51:22 +00:00

mcndave added this to the Version 2.0 milestone 2023-02-02 13:51:47 +00:00

mcndave closed this issue

2023-02-02 19:10:09 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: mcndave/picea#6