-
Notifications
You must be signed in to change notification settings - Fork 82
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
FR: YAML Title Alias should Allow Users to Specify Key for Where to Store Title as a Reference #561
Comments
I don't think I follow this request since you can turn off the use of the key |
The purpose of This key is, however, always identical to the YAML |
That may be the case however they are two separate rules that allow for what you are referring to. Enabling both at the same time would then be able to cause unexpected results and would not be something that could be easily fixed. I don't see a problem with making the key used user defined as long as it is sensible that the user should know that using the two rules in conjunction can cause unexpected bugs. Does that make sense or is this something that you think would be prone to bugs? |
Unfortunately I don't know the inner workings of the plugin, so it's difficult for me to judge how bug-prone any of the solutions would be. As a user, however, if there was a possibility to change the tag from |
The change for this has been merged into master and should be in the next release. Please let us know if there are issues with it in either place. Thanks! |
Problem description
Under
YAML Title Alias
there is the setting to "Use the YAML keylinter-yaml-title-alias
to help with filename and heading changes". Currently it creates the key that has identical contents to thetitle
key, so every file has 2 identical keys.Possible solution
Is it possible that instead of
linter-yaml-title-alias
it would use thetitle
key?The text was updated successfully, but these errors were encountered: