[GH-ISSUE #1133] [Feature] More sort options support #763

Closed
opened 2026-03-03 01:05:49 +03:00 by kerem · 4 comments
Owner

Originally created by @bigsk05 on GitHub (Dec 30, 2025).
Original GitHub issue: https://github.com/certimate-go/certimate/issues/1133

Description / 功能描述

For example,

  1. Sort workflows by Scheduled Trigger
  2. Sort workflows by Created Time
  3. Sort Credentials (Provider, Certificate Authority, Notification Channels) by Created Time

Motivation / 请求动机

This will make multi-workflow management much easier and clearer.

Miscellaneous / 其他

No response

Contribution / 贡献代码

  • I am interested in contributing a PR for this! / 我乐意为此提交代码并发起 PR!
Originally created by @bigsk05 on GitHub (Dec 30, 2025). Original GitHub issue: https://github.com/certimate-go/certimate/issues/1133 ### Description / 功能描述 For example, 1. Sort workflows by Scheduled Trigger 2. Sort workflows by Created Time 3. Sort Credentials (Provider, Certificate Authority, Notification Channels) by Created Time ### Motivation / 请求动机 This will make multi-workflow management much easier and clearer. ### Miscellaneous / 其他 _No response_ ### Contribution / 贡献代码 - [ ] I am interested in contributing a PR for this! / 我乐意为此提交代码并发起 PR!
kerem 2026-03-03 01:05:49 +03:00
Author
Owner

@fudiwei commented on GitHub (Jan 4, 2026):

Sort workflows by Scheduled Trigger

I understand your intent, but this is not a straightforward thing. CRON exprs are stored as strings, and when sorted, they are ordered by ASCII sequence rather than actual numeric value.

For example, suppose we have three trigger times: 30 * * * *, 14 * * * *, and 8 * * * *. From a human-readable perspective, we would expect:

  • 8 * * * *
  • 14 * * * *
  • 30 * * * *

However, if sorted by ASCII, the result would be:

  • 14 * * * *
  • 30 * * * *
  • 8 * * * *

And this is only considering the minute field. The situation becomes even more complicated if we take into account the hour or other units.

I believe this kind of sorting result makes little practical sense.


Sort workflows by Created Time
Sort Credentials (Provider, Certificate Authority, Notification Channels) by Created Time

The current default sorting behavior is exactly as you described.

<!-- gh-comment-id:3708087319 --> @fudiwei commented on GitHub (Jan 4, 2026): > Sort workflows by Scheduled Trigger I understand your intent, but this is not a straightforward thing. CRON exprs are stored as strings, and when sorted, they are ordered by ASCII sequence rather than actual numeric value. For example, suppose we have three trigger times: `30 * * * *`, `14 * * * *`, and `8 * * * *`. From a human-readable perspective, we would expect: - `8 * * * *` - `14 * * * *` - `30 * * * *` However, if sorted by ASCII, the result would be: - `14 * * * *` - `30 * * * *` - `8 * * * *` And this is only considering the minute field. The situation becomes even more complicated if we take into account the hour or other units. I believe this kind of sorting result makes little practical sense. --- > Sort workflows by Created Time > Sort Credentials (Provider, Certificate Authority, Notification Channels) by Created Time The current default sorting behavior is exactly as you described.
Author
Owner

@bigsk05 commented on GitHub (Jan 4, 2026):

To the function of sorting workflows by Scheduled Trigger, I think we can provide a parser for sorting like:
sort(function(expr){return PARSED_EXPR_RESULT})
And to the function of:

Sort workflows by Created Time
Sort Credentials (Provider, Certificate Authority, Notification Channels) by Created Time

Actually, I mean add a function to allow the user change des/asc for these options.
I'm using v0.4.12, and I did not find the function I said above.

<!-- gh-comment-id:3708095534 --> @bigsk05 commented on GitHub (Jan 4, 2026): To the function of sorting workflows by Scheduled Trigger, I think we can provide a parser for sorting like: sort(function(expr){return PARSED_EXPR_RESULT}) And to the function of: > Sort workflows by Created Time > Sort Credentials (Provider, Certificate Authority, Notification Channels) by Created Time Actually, I mean add a function to allow the user change des/asc for these options. I'm using v0.4.12, and I did not find the function I said above.
Author
Owner

@fudiwei commented on GitHub (Jan 4, 2026):

Unfortunately, the DB (based on PocketBase) does not support this functionality. Unless you plan to load all the data at once and implement pagination on the frontend, but that is unacceptable.

<!-- gh-comment-id:3708157353 --> @fudiwei commented on GitHub (Jan 4, 2026): Unfortunately, the DB (based on PocketBase) does not support this functionality. Unless you plan to load all the data at once and implement pagination on the frontend, but that is unacceptable.
Author
Owner

@bigsk05 commented on GitHub (Jan 4, 2026):

Well, it's a true problem. I have no idea how to solve this problem.
What about the other two problems?

<!-- gh-comment-id:3708208589 --> @bigsk05 commented on GitHub (Jan 4, 2026): Well, it's a true problem. I have no idea how to solve this problem. What about the other two problems?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/certimate#763
No description provided.