Skip to content
This repository has been archived by the owner on Sep 11, 2024. It is now read-only.

Table: changing dtSortActive is not updating boldness of new column #619

Closed
areknow opened this issue Feb 18, 2020 · 1 comment · Fixed by #620
Closed

Table: changing dtSortActive is not updating boldness of new column #619

areknow opened this issue Feb 18, 2020 · 1 comment · Fixed by #620
Assignees
@tomheller
Labels
bug A broken behaviour that was working previously has-pr P3 Important issue that needs to be resolved

Comments

@areknow
Copy link
Contributor

areknow commented Feb 18, 2020

Bug Report

Expected Behavior

I expect a column to be bold when a matching value has been passed to dtSortActive.

Current Behavior

The column does not become bold. The previous column remains bold. The new column shows the updated directional arrows.

Steps to Reproduce

https://stackblitz.com/edit/github-iwfjnb

Used Versions:

All latest versions in stackblitz example.
@areknow areknow added the bug A broken behaviour that was working previously label Feb 18, 2020
tomheller added a commit that referenced this issue Feb 19, 2020
@tomheller
fix(table): Fixes an issue where the sorting did not update when active
e9d0a13 
binding was updated.

When the active input for the [dtSort] was bound to a member, and this
member was updated, the table did not react to the sorting.

Fixes #619
@tomheller tomheller mentioned this issue Feb 19, 2020
Merged
4 tasks
@tomheller tomheller added has-pr P3 Important issue that needs to be resolved labels Feb 19, 2020
@tomheller tomheller self-assigned this Feb 19, 2020
@tomheller
Copy link
Collaborator

Hi @areknow! Thank you for reporting this. We were able to reproduce the problem and introduce a fix in #620.

tomheller added a commit that referenced this issue Feb 19, 2020
@tomheller
fix(table): Fixes an issue where the sorting did not update when active
04bed13 
binding was updated.

When the active input for the [dtSort] was bound to a member, and this
member was updated, the table did not react to the sorting.

Fixes #619
github-actions bot pushed a commit that referenced this issue Feb 19, 2020
@tomheller
fix(table): Fixes an issue where the sorting did not update when active
6714c25 
binding was updated.

When the active input for the [dtSort] was bound to a member, and this
member was updated, the table did not react to the sorting.

Fixes #619
github-actions bot pushed a commit that referenced this issue Feb 19, 2020
@tomheller
fix(table): Fixes an issue where the sorting did not update when active
47cea95 
binding was updated.

When the active input for the [dtSort] was bound to a member, and this
member was updated, the table did not react to the sorting.

Fixes #619
yngrdyn pushed a commit to yngrdyn/barista that referenced this issue Nov 9, 2020
@tomheller
fix(table): Fixes an issue where the sorting did not update when active
7313a07 
binding was updated.

When the active input for the [dtSort] was bound to a member, and this
member was updated, the table did not react to the sorting.

Fixes dynatrace-oss#619
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@tomheller tomheller

Labels
bug A broken behaviour that was working previously has-pr P3 Important issue that needs to be resolved
Projects
None yet
Milestone
No milestone
2 participants
@tomheller @areknow