[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Grégory Joseph updated MAGNOLIA-1641:
-------------------------------------

    Fix Version/s: 4.3
                       (was: Orange)
      Description: 
--See TODOs in MockUtil : we should make the "properties" format used to create 
MockHierarchyManagers simpler (there are currently several inconsistent ways of 
creating node properties for instance)--

After a quick discussion, we came up with the following syntax. We tried to be 
consistent, non-intrusive and non-ambiguous.
{code}
/path/to/node@                      create empty node if it does not exist - 
default type if not specified via other line, unspecified UUID if not specified 
via other line
/path/to/n...@uuid=some-uuid        specifies UUID - create empty node if it 
does not exist, default type if not specified via other line
/path/to/n...@type=foo:bar          specifies NT - create empty node if it does 
not exist, unspecified UUID if not specified via other property
/path/to/node/property=value        default property type - create node if it 
does not exist - default node type if not specified
/path/to/node/property#date=value   specified property type and conversion - 
create node if it does not exist - default node type if not specified
/path/to/node/property#string=      empty string property - create node if it 
does not exist - default node type if not specified
/path/to/node/property#             empty string property - create node if it 
does not exist - default node type if not specified
{code}

We'll have to cleanup our current tests, obviously, but since this is not 
something that will affect running systems (only poor developers who decide to 
switch their dev project to 4.3), we'll drop the support for the old syntax 
right away.

  was:See TODOs in MockUtil : we should make the "properties" format used to 
create MockHierarchyManagers simpler (there are currently several inconsistent 
ways of creating node properties for instance)


> Review mock properties syntax
> -----------------------------
>
>                 Key: MAGNOLIA-1641
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-1641
>             Project: Magnolia
>          Issue Type: Improvement
>          Components: core
>            Reporter: Grégory Joseph
>            Assignee: Grégory Joseph
>             Fix For: 4.3
>
>
> --See TODOs in MockUtil : we should make the "properties" format used to 
> create MockHierarchyManagers simpler (there are currently several 
> inconsistent ways of creating node properties for instance)--
> After a quick discussion, we came up with the following syntax. We tried to 
> be consistent, non-intrusive and non-ambiguous.
> {code}
> /path/to/node@                      create empty node if it does not exist - 
> default type if not specified via other line, unspecified UUID if not 
> specified via other line
> /path/to/n...@uuid=some-uuid        specifies UUID - create empty node if it 
> does not exist, default type if not specified via other line
> /path/to/n...@type=foo:bar          specifies NT - create empty node if it 
> does not exist, unspecified UUID if not specified via other property
> /path/to/node/property=value        default property type - create node if it 
> does not exist - default node type if not specified
> /path/to/node/property#date=value   specified property type and conversion - 
> create node if it does not exist - default node type if not specified
> /path/to/node/property#string=      empty string property - create node if it 
> does not exist - default node type if not specified
> /path/to/node/property#             empty string property - create node if it 
> does not exist - default node type if not specified
> {code}
> We'll have to cleanup our current tests, obviously, but since this is not 
> something that will affect running systems (only poor developers who decide 
> to switch their dev project to 4.3), we'll drop the support for the old 
> syntax right away.

-- 
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/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to