mirror of
https://github.com/certimate-go/certimate.git
synced 2026-04-25 20:55:52 +03:00
[GH-ISSUE #1133] [Feature] More sort options support #763
Labels
No labels
announcement
backlog
bug
declined
documentation
duplicate
enhancement
good first issue
good first issue
help wanted
invalid
pull-request
question
stale
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/certimate#763
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bigsk05 on GitHub (Dec 30, 2025).
Original GitHub issue: https://github.com/certimate-go/certimate/issues/1133
Description / 功能描述
For example,
Motivation / 请求动机
This will make multi-workflow management much easier and clearer.
Miscellaneous / 其他
No response
Contribution / 贡献代码
@fudiwei commented on GitHub (Jan 4, 2026):
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 * * * *, and8 * * * *. 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.
The current default sorting behavior is exactly as you described.
@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:
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.
@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.
@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?