UX: Messages: Use "Newest" as default mode

[polegkashti]

• Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
Simply chaned the default filter mode.

Is there anything you'd like reviewers to focus on?
Hi, I’ve noticed that other users have also expressed a need for this change, and some of our Kafka users specifically mentioned it. I believe it’s a great idea to modify the default mode, as it aligns better with Kafka's real-time streaming nature.

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

• No need to
• Manually (please, describe, if necessary)
• Unit checks
• Integration checks
• Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
• My changes generate no new warnings (e.g. Sonar is happy)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)

[polegkashti]

resolves #570

[fallen-up]

i tried to solve the problem this way. as a result "Newest" is displayed in the UI, but sometimes the messages are empty. only changing to "Oldest" and then back to "Newest" helps.

[Haarolean]

i tried to solve the problem this way. as a result "Newest" is displayed in the UI, but sometimes the messages are empty. only changing to "Oldest" and then back to "Newest" helps.

should be working, as we have const defaultModeValue = ModeOptions[0].value; in useMEssageFilters.ts. @polegkashti can you confirm?

[polegkashti]

i tried to solve the problem this way. as a result "Newest" is displayed in the UI, but sometimes the messages are empty. only changing to "Oldest" and then back to "Newest" helps.

should be working, as we have const defaultModeValue = ModeOptions[0].value; in useMEssageFilters.ts. @polegkashti can you confirm?

Based on my testing, everything is functioning properly, and I don't see any reason for this issue to occur.

[fallen-up]

i have tested both options (they are essentially identical).
1)

export const ModeOptions = [
  { value: PollingMode.EARLIEST, label: 'Oldest' },
  { value: PollingMode.LATEST, label: 'Newest' },
  { value: PollingMode.TAILING, label: 'Live' },
  { value: PollingMode.FROM_OFFSET, label: 'From offset' },
  { value: PollingMode.TO_OFFSET, label: 'To offset' },
  { value: PollingMode.FROM_TIMESTAMP, label: 'Since time' },
  { value: PollingMode.TO_TIMESTAMP, label: 'To time' },
];

in frontend/src/lib/hooks/filterUtils.ts
+
const defaultModeValue = ModeOptions[1].value;
in frontend/src/lib/hooks/useMessagesFilters.ts
2)

export const ModeOptions = [
  { value: PollingMode.LATEST, label: 'Newest' },
  { value: PollingMode.EARLIEST, label: 'Oldest' },
  { value: PollingMode.TAILING, label: 'Live' },
  { value: PollingMode.FROM_OFFSET, label: 'From offset' },
  { value: PollingMode.TO_OFFSET, label: 'To offset' },
  { value: PollingMode.FROM_TIMESTAMP, label: 'Since time' },
  { value: PollingMode.TO_TIMESTAMP, label: 'To time' },
];

in frontend/src/lib/hooks/filterUtils.ts
+
const defaultModeValue = ModeOptions[0].value;
in frontend/src/lib/hooks/filterUtils.ts

the result is the same. sometimes it works (in most cases), sometimes it doesn't. maybe there is some other forgotten part of the code?

p.s.: it's not compacted topic

[polegkashti]

I tested the change again with a variety of messages and was unable to reproduce the issue. Additionally, I reviewed the codebase for any other references to the "Newest" filter and found no related components.

Given this, I believe there isn't a valid reason to withhold approval for this pull request. If the issue continues to affect you, I recommend opening a new issue with more details to help us investigate further :)

[Haarolean]

@polegkashti thank you!