casey
support wildcard imports in justfiles
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/git.just'
import '.just/poetry.just'
import '.just/precommit.just'
...
...
I prefer to import all files via wildcard:
import '.just/*.just'
...
I think this is actually pretty doable. This is technically a breaking change, since someone could have a path with * in it, which this would break, but that's so vanishingly rare I think we can do this without worrying. This would make a great first issue if anyone feels like taking a crack at it.
related to imports: how difficult would it be to support import by url?
import http://example.com/justfile
related to imports: how difficult would it be to support import by url?
This was discussed in https://github.com/casey/just/issues/1799
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. https://gitlab.com/shardus/shardus-net
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. https://www.linkedin.com/in/abdulazeem-shaik/
Can contribute in TypeScript (Node.js), Rust, Java & Kotlin (Android App Dev), and C++ ( Competitive Programming ).
This issue is basically about the same as this one. This PR shoud be worked on for implementing this feature.
@BoolPurist what is blocking this PR https://github.com/casey/just/pull/2376?
This issue was tagged as "good first issue", but implementation is more complicated then expected?
@BoolPurist what is blocking this PR https://github.com/casey/just/pull/2376?
From what I can tell this PR https://github.com/casey/just/pull/2376 is simply not worked on anymore by the original author of this PR. Last commit was Oct 12, 2024, see last commit of PR https://github.com/casey/just/pull/2376/commits/ec7c1d23722c6012708535b11490af05b9b0d77e, quite a while ago.
This issue was tagged as "good first issue", but implementation is more complicated then expected?
My guess is yes when I look at the comments of PR https://github.com/casey/just/pull/2376. To me. The arosen complexity boild down to this comment
I think it is best to wait for @casey opinion on how to proceed with this implementation especially with the existing PR.