-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
When issue template name ends with .yaml/.yml call the yamlParser #23719
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
Closed
zeripath
wants to merge
5
commits into
go-gitea:main
from
zeripath:fix-23715-do-not-call-legacy-for-yaml-templates
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
5f19f54
Ensure that label filename extensions are removed when setting up rep…
zeripath f670840
Ensure that legacy formats within customPath still override builtins
zeripath 4201a37
oops
zeripath 07bac3f
fix static build
zeripath e43bd49
Merge remote-tracking branch 'origin/main' into fix-23715-do-not-call…
zeripath File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
I do not understand why it should remove the extensions. It looks hacky and forces other code to "guess" the file name again and again.
And could there be a case like this:
IIRC the
options
package tries the custom directory first and then the builtin assets.custom/Advance.yml
andstatic/Advance.yaml
load("Advance")
triesAdvance.yaml
first, it would always loadstatic/Advance.yaml
?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.
I think it's completely reasonable to hide the extension - however, this does make overriding a little bit more complex.
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.
Or could the extension just be hidden on the UI? But always use the filename with extension internally?
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.
How do you think about this proposal? I think it has more Pros and less Cons than current PR's approach.
We have already been doing the best to avoid guess "refs" for branch/tag/commits. Now, I don't think it makes sense to guess the extensions.
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.
you can't guarantee that the templates file hasn't been changed on the filesystem. So - therefore you cannot know the extension at the time of looking up the file.
Therefore you need to guess.
Uh oh!
There was an error while loading. Please reload this page.
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.
My proposal is Respect the origin file names of option items #23749
I think we do not need to guess. If you think there is any problem, please help to design a case for it (to help me to understand the problem).