-
Notifications
You must be signed in to change notification settings - Fork 500
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
support wildcard imports if justfiles #1885
Comments
I think this is actually pretty doable. This is technically a breaking change, since someone could have a path with |
related to imports: how difficult would it be to support import by url?
|
This was discussed in #1799 |
Hi! |
I don't really assign issues, but you're free to take a crack at it! I'm super slammed at the moment with another project, so I might not be able to review any PRs for a month or more. |
Oh, that's alright. I shall try to fix this. btw if you do need any help on your project, I'm happy to help. I have experience contributing full-time to a TCP socket communication library that facilitates p2p networking for the Shardeum blockchain, using Neon bindings, Rust, and Tokio. I am just trying to make some contributions to the open-source community. Although I am not a new programmer / developer, I am new to open source and I want to get used to contributing to random codebases. Can contribute in TypeScript (Node.js), Rust, Java & Kotlin (Android App Dev), and C++ ( Competitive Programming ). |
In order to create re-usable toplevel justfiles, I started to split them up per command/tool in a .just-subfolder
For the moment I need to import them file by file and hardcoded each filename:
import '.just/*.just'
...
The text was updated successfully, but these errors were encountered: