-
-
Notifications
You must be signed in to change notification settings - Fork 290
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
clj-kondo Pod - lint stdin #2285
Projects
Comments
Note to self: this can be fixed by migrating the pod to use sockets instead of stdin. |
borkdude
moved this from High priority (next release)
to Medium priority (new / enhance)
in clj-kondo
Mar 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
[ Leave this text in if you want to promote it. ]
To upvote this issue, give it a thumbs up. See this list for the most upvoted issues.
[ To keep development of this project going, consider sponsoring. If you are
already a sponsor, thank you! You can remove this message. ]
Is your feature request related to a problem? Please describe.
It's not a problem, but it would be great to be able to lint from standard input when using clj-kondo Pod. Currently, the following doesn't work:
A workaround is to create a file, and then lint the file.
Describe the solution you'd like
Is it reasonable to expect it to work like the clj-kondo JVM API? So it's possible to lint from standard input like it's supported on the JVM.
The text was updated successfully, but these errors were encountered: