[
https://issues.apache.org/jira/browse/IGNITE-7395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Borisov updated IGNITE-7395:
---------------------------------
Description:
*The problem:*
The only way to access an item instance from inside list-editable transclusion
slots is via _$parent.item_. This approach is both cumbersome and prone to
$scope-related issues (i.e. input elements can't access it if there are
intermidate scopes).
*What to do:*
Provide an easy and reliable way to access item (maybe as _$item_?) variable.
It would also be handy to be able to change item alias name (useful for nested
list-editable's).
was:
*The problem:*
The only way to access an item instance from inside list-editable transclusion
slots is via _$parent.item_. This approach is both cumbersome and prone to
$scope-related issues (i.e. input elements can't access it if there are
intermidate scopes).
*What to do:*
Provide an easy and reliable way to access item (maybe as _$item_?) and
_$index_ variables (used by unique ignite-validator). It would also be handy to
be able to change item alias name (useful for nested list-editable's).
> Web console: improve list-editable scope variables access
> ---------------------------------------------------------
>
> Key: IGNITE-7395
> URL: https://issues.apache.org/jira/browse/IGNITE-7395
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
> Reporter: Ilya Borisov
> Assignee: Ilya Borisov
> Priority: Minor
>
> *The problem:*
> The only way to access an item instance from inside list-editable
> transclusion slots is via _$parent.item_. This approach is both cumbersome
> and prone to $scope-related issues (i.e. input elements can't access it if
> there are intermidate scopes).
> *What to do:*
> Provide an easy and reliable way to access item (maybe as _$item_?) variable.
> It would also be handy to be able to change item alias name (useful for
> nested list-editable's).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
