Mailing-List: contact issues-help@ariatosca.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ariatosca.incubator.apache.org
Date: Sun, 28 May 2017 08:27:04 +0000 (UTC)
From: "Maxim Orlov (JIRA)" <jira@apache.org>
To: issues@ariatosca.apache.org
Message-ID: <JIRA.13075442.1495959598000.311305.1495960024038@Atlassian.JIRA>
In-Reply-To: <JIRA.13075442.1495959598000@Atlassian.JIRA>
References: <JIRA.13075442.1495959598000@Atlassian.JIRA> <JIRA.13075442.1495959598380@jira-lw-us.apache.org>
Subject: [jira] [Updated] (ARIA-262) Inconsistent ARIA attributes behavior
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 28 May 2017 08:27:09 -0000


     [ https://issues.apache.org/jira/browse/ARIA-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Orlov updated ARIA-262:
-----------------------------
    Description: 
ARIA provides sugaring for node attributes. However this sugaring is somewhat limited, as it sugars ctx accessed attributes. e.g. Under NodeOperationContext {{ctx.node.attributes}} has a dict-like behavior, where the value is another object with a dict-like behavior. This is provided by the sugaring. 
However {{ctx.node.relationships[0].target_node.attributes}} provides a dict where the value is of type Parameter, accessing the value of this Parameter require `param. This creates inconsistency with regards to access to attributes.

There are several possible solutions:
1. Enable sugaring on the model level. this will effectively make the creation of Parameter implicit, but this will be possible throughout the entire code (not only under context).
2. Enable sugaring by tapping to sqla events and altering the return values. 

  was:
ARIA provides sugaring for node attributes. However this sugaring is somewhat limited, as it sugars ctx accessed attributes. e.g. Under NodeOperationContext {{ctx.node.attributes}} has a dict-like behavior, where the value is another object with a dict-like behavior. This is provided by the sugaring. 
However {{ctx.node.relationships[0].target_node.attributes` provides a dict where the value is of type Parameter, accessing the value of this Parameter require `param. This creates inconsistency with regards to access to attributes.

There are several possible solutions:
1. Enable sugaring on the model level. this will effectively make the creation of Parameter implicit, but this will be possible throughout the entire code (not only under context).
2. Enable sugaring by tapping to sqla events and altering the return values. 


> Inconsistent ARIA attributes behavior
> -------------------------------------
>
>                 Key: ARIA-262
>                 URL: https://issues.apache.org/jira/browse/ARIA-262
>             Project: AriaTosca
>          Issue Type: Story
>            Reporter: Maxim Orlov
>
> ARIA provides sugaring for node attributes. However this sugaring is somewhat limited, as it sugars ctx accessed attributes. e.g. Under NodeOperationContext {{ctx.node.attributes}} has a dict-like behavior, where the value is another object with a dict-like behavior. This is provided by the sugaring. 
> However {{ctx.node.relationships[0].target_node.attributes}} provides a dict where the value is of type Parameter, accessing the value of this Parameter require `param. This creates inconsistency with regards to access to attributes.
> There are several possible solutions:
> 1. Enable sugaring on the model level. this will effectively make the creation of Parameter implicit, but this will be possible throughout the entire code (not only under context).
> 2. Enable sugaring by tapping to sqla events and altering the return values. 


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)