[
https://issues.apache.org/jira/browse/IGNITE-11338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771665#comment-16771665
]
Ilya Borisov commented on IGNITE-11338:
---------------------------------------
[~kuaw26] the issue was caused by a combination of several factors:
1. Basic configuration sorts caches by name.
2. Basic configuration cache changes are applied immediately and not on input
blur.
3. <list-editable> component tracks items in edit most by index and not id.
To fix it, I updated all item operation in list-editable to use computed id
instead of index. I also converted most of list-editable extra
directives/components to TS in order to ensure correct list-editable controller
method call signatures.
> Web Console: Current cache "jump" after edit on "Basic configuration" screen
> ----------------------------------------------------------------------------
>
> Key: IGNITE-11338
> URL: https://issues.apache.org/jira/browse/IGNITE-11338
> Project: Ignite
> Issue Type: Bug
> Components: wizards
> Reporter: Alexey Kuznetsov
> Assignee: Ilya Borisov
> Priority: Major
> Time Spent: 1h 13m
> Remaining Estimate: 0h
>
> Steps to reproduce:
> # Create new cluster.
> # Add 3 caches (just click 3 times on "Add new cache")
> # Click on first cache with name "Cache" and add a letter "x" to the end of
> its name.
> # It will "jump" to the end of list.
> # And current "editable" item become cache with name "Cache1"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
