The table sorting functionality was emitting multiple events when sorting by a different column, causing a "double emit" issue that could confuse developers and lead to unexpected behavior in applications.

Problem:
When sorting by a different column key, the updateSorterAndDirection method was calling both updateDirection(1) and updateSorter(sorter) separately, which caused:

1. directionChange event to be emitted first
2. sorterChange event to be emitted second
3. Both events triggering separate change detection cycles

This resulted in what users perceived as "double emit" of sorting events.

Solution:
Introduced atomic updates when sorting by a different key by:

• Adding a new private method updateSorterAndDirectionAtomically that updates both internal state and emits events together in the same execution context
• Modifying updateSorterAndDirection to use atomic updates for different keys while preserving existing behavior for same-key sorting (direction toggle)
• Ensuring backward compatibility with all existing functionality

Changes:

• Modified TuiTableDirective.updateSorterAndDirection() to handle different-key sorting atomically
• Added comprehensive test coverage to prevent regressions
• Maintained all existing behavior for same-column sorting scenarios

The fix ensures that when sorting by a different column, both directionChange and sorterChange events are emitted together in the same execution context, eliminating the perception of double emissions while maintaining full backward compatibility.

Fixes #11420.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.