- Notifications
You must be signed in to change notification settings - Fork1k
feat: support custom order of agent metadata#12066
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
stringscript=3; | ||
int64interval=4; | ||
int64timeout=5; | ||
int64order=6; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Unfortunate that it generates an int64 here for an int32 :\
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Yeah, this is unfortunate. It is aligned withcoder_parameter
display order type though.
Taking back to draft, as I can't update the workspace after removing
|
Uh oh!
There was an error while loading.Please reload this page.
Fixes:#8487
This PR modifies the logic responsible for sorting agent metadata items to consider custom ordering, not just keys.