-
Notifications
You must be signed in to change notification settings - Fork 87
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: YAML Key Sort Does Not Work when There is Trailing Whitespace after a Colon in Config Values #1202
Comments
Hey @MrJohnWilkinson . I am going to need your |
Thanks. Everything you need should be below Cheers Content before running linter
content after running linter
Linter yaml-key-sort setting
Linter log
and the data.json file
|
I think I see the issue, but I need to double check. It looks like the keys in the settings you provided have a colon at the end of them, but keys should not have a colon in them. |
Yeah. Currently there is nothing in place to handle the specified keys have a colon at the end of them. They also should not have any spaces whitespace after the end of the name except the newline character. So it looks like if you remove the ending colons and spaces if there are any from those values and it should work. Is there a better way I can present this setting to make it easier to input value to sort by? I am guessing something more akin to what is present for custom commands or custom regex. |
I do think the issue is the whitespace after a couple of the values. I can make a couple of changes that should make it play nice, but I am guessing making the change to where the settings are input will likely make it easier for people in the long run. |
Working like a charm! Thanks!
Kind regards,
John Wilkinson
Product Manager
3DVR Solutions
Mobile: +61 (0)423 094 769
<https://www.3dvrs.com> https://www.3dvrs.com
***@***.***> ***@***.***
This communication may contain information that is privileged, confidential, and / or exempt from disclosure under applicable law; and is intended only for the named addressee. If you are not the intended recipient you should not disseminate, distribute, use or copy this e-mail message or any information contained in, or attached to, this message. Please notify 3DVR Solutions immediately by e-mail if you have received this e-mail message by mistake; and delete this e-mail message from your system. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus-free. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this e-mail message which may arise as a result of e-mail transmission. Service of proceedings and legal documents is not accepted by email.
From: Peter Kaufman ***@***.***>
Sent: Saturday, 26 October 2024 09:35
To: platers/obsidian-linter ***@***.***>
Cc: MrJohnWilkinson ***@***.***>; Mention ***@***.***>
Subject: Re: [platers/obsidian-linter] Bug: yaml key sort is broken (Issue #1202)
I do think the issue is the whitespace after a couple of the values. I can make a couple of changes that should make it play nice, but I am guessing making the change to where the settings are input will likely make it easier for people in the long run.
—
Reply to this email directly, view it on GitHub <#1202 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BACYTMZPVG2SIURCV7T5YFLZ5LITLAVCNFSM6AAAAABQLGRTQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZGA2DENRZHE> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/BACYTM7IV27ANGCUMJSFSJLZ5LITLA5CNFSM6AAAAABQLGRTQKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTURMDLIW.gif> Message ID: ***@***.*** ***@***.***> >
|
Just to clarify for you., No issue with the colon, which is the default that obsidian puts in there anyway so you’d want to handle that. The issue was white spaces after the keys.
Thanks again!
Kind regards,
John Wilkinson
Product Manager
3DVR Solutions
Mobile: +61 (0)423 094 769
<https://www.3dvrs.com> https://www.3dvrs.com
***@***.***> ***@***.***
This communication may contain information that is privileged, confidential, and / or exempt from disclosure under applicable law; and is intended only for the named addressee. If you are not the intended recipient you should not disseminate, distribute, use or copy this e-mail message or any information contained in, or attached to, this message. Please notify 3DVR Solutions immediately by e-mail if you have received this e-mail message by mistake; and delete this e-mail message from your system. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus-free. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this e-mail message which may arise as a result of e-mail transmission. Service of proceedings and legal documents is not accepted by email.
From: Peter Kaufman ***@***.***>
Sent: Saturday, 26 October 2024 09:35
To: platers/obsidian-linter ***@***.***>
Cc: MrJohnWilkinson ***@***.***>; Mention ***@***.***>
Subject: Re: [platers/obsidian-linter] Bug: yaml key sort is broken (Issue #1202)
I do think the issue is the whitespace after a couple of the values. I can make a couple of changes that should make it play nice, but I am guessing making the change to where the settings are input will likely make it easier for people in the long run.
—
Reply to this email directly, view it on GitHub <#1202 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BACYTMZPVG2SIURCV7T5YFLZ5LITLAVCNFSM6AAAAABQLGRTQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZGA2DENRZHE> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/BACYTM7IV27ANGCUMJSFSJLZ5LITLA5CNFSM6AAAAABQLGRTQKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTURMDLIW.gif> Message ID: ***@***.*** ***@***.***> >
|
Thanks for the update! I am working on an automatic fix for that whitespace issue. I may even update how that setting is displayed and whatnot to help keep bad input from being added. |
Nice one. Love your work! Thanks
Kind regards,
John Wilkinson
Product Manager
3DVR Solutions
Mobile: +61 (0)423 094 769
<https://www.3dvrs.com> https://www.3dvrs.com
***@***.***> ***@***.***
This communication may contain information that is privileged, confidential, and / or exempt from disclosure under applicable law; and is intended only for the named addressee. If you are not the intended recipient you should not disseminate, distribute, use or copy this e-mail message or any information contained in, or attached to, this message. Please notify 3DVR Solutions immediately by e-mail if you have received this e-mail message by mistake; and delete this e-mail message from your system. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus-free. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this e-mail message which may arise as a result of e-mail transmission. Service of proceedings and legal documents is not accepted by email.
From: Peter Kaufman ***@***.***>
Sent: Saturday, 26 October 2024 19:37
To: platers/obsidian-linter ***@***.***>
Cc: MrJohnWilkinson ***@***.***>; Mention ***@***.***>
Subject: Re: [platers/obsidian-linter] Bug: yaml key sort is broken (Issue #1202)
Thanks for the update! I am working on an automatic fix for that whitespace issue. I may even update how that setting is displayed and whatnot to help keep bad input from being added.
—
Reply to this email directly, view it on GitHub <#1202 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BACYTM5BDQSEHDOWSLJ2WODZ5NPEJAVCNFSM6AAAAABQLGRTQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZGQ2DSMJZGA> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/BACYTM2425OAW6PFPUHDONLZ5NPEJA5CNFSM6AAAAABQLGRTQKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTURM4FGM.gif> Message ID: ***@***.*** ***@***.***> >
|
I believe I have a fix. It will hopefully get added soon. I just need to verify all the CI checks pass. |
The change has been merged and should go out with the next release. Please let us know if the issue persists on master or in the next release. |
Nicely done. Thanks. Will do
Kind regards,
John Wilkinson
Product Manager
3DVR Solutions
Mobile: +61 (0)423 094 769
<https://www.3dvrs.com> https://www.3dvrs.com
***@***.***> ***@***.***
This communication may contain information that is privileged, confidential, and / or exempt from disclosure under applicable law; and is intended only for the named addressee. If you are not the intended recipient you should not disseminate, distribute, use or copy this e-mail message or any information contained in, or attached to, this message. Please notify 3DVR Solutions immediately by e-mail if you have received this e-mail message by mistake; and delete this e-mail message from your system. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus-free. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this e-mail message which may arise as a result of e-mail transmission. Service of proceedings and legal documents is not accepted by email.
From: Peter Kaufman ***@***.***>
Sent: Monday, 28 October 2024 02:55
To: platers/obsidian-linter ***@***.***>
Cc: MrJohnWilkinson ***@***.***>; Mention ***@***.***>
Subject: Re: [platers/obsidian-linter] Bug: YAML Key Sort Does Not Work when There is Trailing Whitespace after a Colon in Config Values (Issue #1202)
The change has been merged and should go out with the next release. Please let us know if the issue persists on master or in the next release.
—
Reply to this email directly, view it on GitHub <#1202 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BACYTMZMB5LQNB2WQSOUKJ3Z5ULFXAVCNFSM6AAAAABQLGRTQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBQGA4TONBQGU> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/BACYTM77EYJITNSYNWV4AP3Z5ULFXA5CNFSM6AAAAABQLGRTQKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTURODXH2.gif> Message ID: ***@***.*** ***@***.***> >
|
Describe the Bug
I put in the keys, i run the lint, orders do change, but not as they should
How to Reproduce
Steps to reproduce the behavior:
pr-type:
pr-urgency:
pr-okr:
pr-completed-date:
related-companies:
pr-priority:
modified: 2024-10-21 09:58
stakeholders:
pr-pipeline-stage:
pr-size:
template: "[[Pro New Project Outcome Template]]"
pr-due-date:
created-date: '[[<% tp.file.creation_date("YYYY-MM-DD") %>]]'
related-companies:
stakeholders:
pr-priority:
pr-pipeline-stage:
pr-size:
pr-type:
pr-okr:
pr-due-date:
pr-urgency:
pr-completed-date:
template:
created-date:
modified:
pr-type:
pr-okr:
pr-completed-date:
related-companies:
stakeholders:
template: "[[Pro New Project Outcome Template]]"
pr-priority:
pr-pipeline-stage:
pr-size:
pr-due-date:
pr-urgency:
created-date: '[[<% tp.file.creation_date("YYYY-MM-DD") %>]]'
modified: 2024-10-21 09:58
Running linter
rules before regular rules: 0.09999990463256836 ms
Running Custom Regex
custom regex rules: 0.10000002384185791 ms
Running YAML Key Sort
yaml-key-sort: 1.100000023841858 ms
pr-type:
pr-okr:
pr-completed-date:
related-companies:
stakeholders:
template: "[[Pro New Project Outcome Template]]"
pr-priority:
pr-pipeline-stage:
pr-size:
pr-due-date:
pr-urgency:
created-date: '[[<% tp.file.creation_date("YYYY-MM-DD") %>]]'
modified: 2024-10-21 09:58
<% await tp.file.move("/CRM/Projects/" + tp.file.title) %>
Navigation
![[🪧 Navigation Template]]
Related discussions
[[Project Prioritisation Matrix]]
Notes
Reference Links
rules after regular rules: 2 ms
rules running: 2.399999976158142 ms
Device
The text was updated successfully, but these errors were encountered: