-
-
Notifications
You must be signed in to change notification settings - Fork 348
plugins/yaml-schema-detect: init #3414
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
base: main
Are you sure you want to change the base?
Conversation
related to: #3328 |
3ffd052
to
62ed348
Compare
62ed348
to
3e5fc2f
Compare
{ | ||
when = !config.plugins.which-key.enable; | ||
message = '' | ||
This plugin requires `plugins.which-key` to be enabled |
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 don't see this requirement mentioned on the plugin's README.
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.
they do not appear to be there, but when I tried running the tests without it it would complain that it needs which-key
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.
It could be an upstream bug; maybe they have which-key integration that forgets to check it is present before importing it?
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.
it's in their init.lua
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.
do you think we could merge it? or should I raise an issue upstream about it?(personally speaking im fine having that warning for the users)
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've opened cwrau/yaml-schema-detect.nvim#6, so let's give upstream a little time to respond.
I don't mind merging if we add references to that issue, but ideally we'd merge once we know what the correct behaviour is.
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.
thank you Matt <3
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 see upstream closed the PR with the additions you mentioned, I guess we can wait for the next round of vimPlugins updates after that I'll rebase and fix the tests, and again thanks Matt :)
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.
bumping this, updated the test removing which-key and removed the warning that mentioned that the plugin requires it, with that I was able to successfully run the tests I'll wait for #3562 to be merged and then I'll rebase and push the commit again to be ready for a review
No description provided.