[
https://issues.apache.org/jira/browse/SLING-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592587#action_12592587
]
Carsten Ziegeler commented on SLING-367:
----------------------------------------
Hmm, I totally agree that things should be as simple as possible and people
should be able to start using Sling without having to mess with too many
details.
But :) if you look at a POST request it should be clearly visible which
parameters make up the content and which not - having to learn a special
exclusion list is neither simple nor intuitiv.
I don't care that much what the prefixes are, but it should be possible to
distinguish them. We could reach the same goal by renaming the sling prefix for
the repository to something else.
> 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.
