Skip to content

feat: detect_extensions, detect_files, and detect_folders for every module #6697

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

Open
mrclrchtr opened this issue Apr 24, 2025 · 2 comments
Open
Labels
✨ enhancement A new feature implementation.

Comments

@mrclrchtr
Copy link

detect_extensions, detect_files, and detect_folders for every module

Is your feature request related to a problem? Please describe.

I would like to be able to switch each module on and off conditionally. Surely it would make sense to simply abstract this and make it generally available or not?

@mrclrchtr mrclrchtr added the ✨ enhancement A new feature implementation. label Apr 24, 2025
@jankatins
Copy link
Contributor

jankatins commented Apr 24, 2025

Probably a duplicate of #4363.

Would #4439 work for your usecase? You can also point STARSHIP_CONFIG to specific configs. Both need something like direnv or mise to switch env vars based on directories.

@mrclrchtr
Copy link
Author

I think, this issue could be the answer for the discussion in #4363.

If I understand the issue #4439 correctly, then not really. It would require me to set environment variables dynamically in the folders, right?

I would simply like to say, for example: if there is a .git folder, then activate module x (because it's in a dev folder). I don't want to have to create extra .env files or anything like that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨ enhancement A new feature implementation.
Projects
None yet
Development

No branches or pull requests

2 participants