[
https://issues.apache.org/jira/browse/SLING-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592373#action_12592373
]
David Nuescheler commented on SLING-367:
----------------------------------------
i think the behavior is consistent if all the form-names that bear any
relevance are
prefixed with "sling:". the fact that some of these sling commands also persist
as a property
is a side effect at best i think.
i think it is very confusing to have to learn all these different conventions
just because some
of the sling related commands are also persisted as content.
Especially since it complicates the "simple" most common case of the usage and
there definitely
is no need for a new "namespace" since users will not make up arbitrary sling
properties,
this will always be avery defined set.
> change sling:post: to sling: for "command" prefixes in form names
> -----------------------------------------------------------------
>
> Key: SLING-367
> URL: https://issues.apache.org/jira/browse/SLING-367
> Project: Sling
> Issue Type: Bug
> Components: Post Servlets
> Reporter: David Nuescheler
>
> I think it is fair to also prefix the form elements that express certain
> "commands"
> with "sling:" since they are sling related.
> i see it more as a side effect that the "sling:resourceType" also gets
> persisted.
> generally, i think everything that has something to with "sling" should be
> prefixed
> with "sling".
> I think we need to make sure that we don't complicate the most simple cases
> just
> to a avoid possible collisions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
