[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Weder updated MAGNOLIA-4572:
------------------------------------
Fix Version/s: 5.0 Alpha1 S9
(was: 5.0)
> Should we use (simple) namespaces for app ids?
> ----------------------------------------------
>
> Key: MAGNOLIA-4572
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4572
> Project: Magnolia
> Issue Type: Improvement
> Security Level: Public
> Components: core
> Reporter: Andreas Weder
> Assignee: Tobias Mattsson
> Priority: Critical
> Fix For: 5.0 Alpha1 S9
>
>
> While reading the ["location, location, location"
> section|http://wiki.magnolia-cms.com/display/DOCS/Location%2C+location%2C+location]
> in the chapter on building apps of the evolving Magnolia 5 book, it occurred
> to me that we could save us some hassle with non-unique app ids, if we'd
> introduce (simple) namespaces.
> Wouldn't it be helpful to *reserve the "mgnl" prefix for us* and then change
> the URLs to become, e.g.:
> {code}#app:mgnl-pages:editor;/mypath/topage:preview{code}
> or
> {code}#shell:mgnl-pulse:inbox{code}
> ?
> That way we could ensure that, should someone indeed unknowingly re-use an
> already used app id such as "pages" or "contacts", Magnolia would still come
> up and work properly. Plus, such a change would also lower the entry barrier
> as I'd expect such errors to be hard to find for Magnolia beginners, even if
> we show a message in the log files.
> We could even go as far and use the same namespace also for sub-app ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
