| Age | Commit message (Collapse) | Author |
|---|
|
Replaces the existing nodejs module end-to-end tests with integration tests that don't require preinstalled environmental dependencies.
- Moved the tests to the same file as the module they test
- Created a render_module utility function for rendering modules within tests
- Removed Node.js installation during CI setup
- Add Shell to Context to allow for tests to not run shell-specific code
|
|
|
|
Closes #656
|
|
|
|
Changes imports statements to make imports more uniform.
|
|
|
|
This PR refactors config and puts configuration files for all modules in `configs/`.
|
|
|
|
|
|
|
|
A couple of optimizations are done in this PR. One, we now will check config ahead of time to see if a module is disabled before running any module code. Also, we won't try to discover a git repository unless the module requests access to it.
|
|
Add parsing logic, config support, docs, and integration with other modules
for custom styling of each module.
|
|
on Zsh, battery percentage character would print %
this PR fixes print %{ -> %
|
|
Co-authored-by: Tiffany Le-Nguyen <tlenguyen@expedia.com>
Co-authored-by: Matan Kushner <hello@matchai.me>
|
|
|
|
• Add support for the disabled configuration option
This will allow you to selectively disable modules that you don't want or need. 😄
• Overwrite starship configuration file path with STARSHIP_CONFIG environment variable
• Write tests for the two configuration options that are available
|
|
- Create `Config` struct that is added to `Context` when initialized
- Read `~/.confg/starship.toml` during initialization (can be updated later to also look at `$XDG_CONFIG_HOME`)
- `Context` now has a method for creating modules. This allows us to provide modules with a reference to the configuration specific to that module
|
|
|
