Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KTable - [Trial] Added changeSort event handler #655

Merged
merged 1 commit into from
Jun 14, 2024

Conversation

BabyElias
Copy link
Contributor

@BabyElias BabyElias commented Jun 13, 2024

Description

  • Added changeSort event handler as discussed for implementation of backend sorting logic. For demo purposes, this table imitates the behaviour of 'Externally sorted on Frontend' tables since there was no backend API that could be used for testing.
  • Enhanced KTable testing conditions.

@MisRob MisRob self-requested a review June 14, 2024 07:49
@MisRob MisRob self-assigned this Jun 14, 2024
@MisRob
Copy link
Member

MisRob commented Jun 14, 2024

Thanks @BabyElias, this reflect well everything we talked about and am pretty confident that it will make the usage of the table for the Kolibri's facility users seamless ;)

@MisRob MisRob merged commit f843b55 into learningequality:gsoc-table Jun 14, 2024
6 of 8 checks passed
@@ -82,6 +88,25 @@
}
});

watch(
Copy link
Member

@MisRob MisRob Jun 14, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is an important piece to ensure reactivity

},
});
const trElements = wrapper.findAll('tbody tr');
expect(trElements.length).toBe(rows.length);
});

it('should emit changeSort event on header click when useLocalSorting is false', async () => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants