Skip to content

Conversation

@tomleb
Copy link
Contributor

@tomleb tomleb commented Nov 27, 2025

Issue rancher/rancher#52780

Unfortunately, we cannot get rid of those columns yet for two reasons:

  1. Duration to Timestamp back to Duration is lossy, doing that for all CRDs would be a regression IMO
  2. The UI doesn't currently work very well with dates that are from CRDs and that aren't the Age column. So instead of showing a pretty printed date, we get Invalid Date column shown. Fixing that involves a bigger change (sending a timestamp instead of duration to the UI which I'm not willing to make from the little time we have before 2.13.1.

So the fix here is adding the missing default columns and calling it a day for now. This PR adds a bunch of tests to try and cover as much as possible so that next time we do make changes, we'll know about regressions and what changes.

@tomleb tomleb requested a review from a team as a code owner November 27, 2025 17:36
- [bar, foo, $skip, $duration]
- schemaID: timestamps.cattle.io.dates
expected:
- [the-date, $duration, $duration, $duration, $timestamp, $duration, $timestamp]
Copy link
Contributor Author

Choose a reason for hiding this comment

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

The $timestamp ones are because the type is a string for those columns

@tomleb tomleb marked this pull request as draft November 27, 2025 18:22
@tomleb
Copy link
Contributor Author

tomleb commented Nov 27, 2025

Seems like this also results in some issues where sorting doesn't work on fields from CRDs 🤔

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.

1 participant