@repokit/core 3.0.0 → 3.0.2

package/Cargo.lock

@@ -239,7 +239,7 @@ checksum = "a96887878f22d7bad8a3b6dc5b7440e0ada9a245242924394987b21cf2210a4c"
 
 [[package]]
 name = "repokit"
-version = "3.0.0"
+version = "3.0.2"
 dependencies = [
  "alphanumeric-sort",
  "colored",

package/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "repokit"
-version = "3.0.0"
+version = "3.0.2"
 edition = "2024"
 
 [[bin]]

package/README.md

@@ -232,47 +232,54 @@ If your command needs to reason about the file system, keep this in mind.
 
 The Repokit CLI can be customized to support themes that better match your team's visual preferences.
 
-Repokit comes with 4 pre-built themes that you can use in your `RepoKitConfig`.
+Repokit comes with 4 pre-built themes that you view by running
 
-```typescript
-import {
-  RepoKitConfig,
-  SeeingRed, // A red theme
-  TheBlues, // A blue theme
-  Green, // A green theme
-} from "@repokit/core";
-
-export const Kit = new RepoKitConfig({
-  project: "My Project",
-  theme: SeeingRed, // Specify a theme here
-});
+```bash
+repokit themes
 ```
 
-By omitting the `theme` property `RepoKit` will use its default visuals.
+To Set your desired theme, you can run
 
-In addition to built-in themes, you can create your own using the `RepoKitTheme`
+```bash
+repokit themes --set <theme-name>
+```
+
+RepoKit also allows you to design your own themes using the `themes` property on your `RepoKitConfig`:
 
 ```typescript
 import { RepoKitConfig, RepoKitTheme } from "@repokit/core";
 
 export const Kit = new RepoKitConfig({
   project: "My Project",
-  theme: new RepoKitTheme({
-    prefixColor: "rgb(220, 36, 91)",
-    commandColor: "rgb(220, 36, 36)",
-    subcommandColor: "rgb(220, 131, 36)",
-    argColor: "rgb(220, 205, 36)",
-    descriptionColor: "rgb(179, 100, 151)",
-    errorPrefixColor: "rgb(220, 36, 39)",
-    highlightColor: "rgb(237, 175, 41)",
-  }),
+  themes: [
+    new RepoKitTheme({
+      name: "my-awesome-theme",
+      colors: {
+        prefixColor: "rgb(220, 36, 91)",
+        commandColor: "rgb(220, 36, 36)",
+        subcommandColor: "rgb(220, 131, 36)",
+        argColor: "rgb(220, 205, 36)",
+        descriptionColor: "rgb(179, 100, 151)",
+        errorPrefixColor: "rgb(220, 36, 39)",
+        highlightColor: "rgb(237, 175, 41)",
+      },
+    }),
+  ],
 });
 ```
 
-All properties on the `RepoKitTheme` are optional overrides for `RepoKit`'s default styling. A color can be any CSS-valid `rgb()` string.
+All properties on the `RepoKitTheme.colors` are optional overrides for `RepoKit`'s default styling. A color can be any CSS-valid `rgb()` string.
 
 <img src="media/seeing-red.webp" width="100%" alt="seeing red theme" />
 
+Once a theme is added to your `RepoKitConfig`, it becomes available by running
+
+```bash
+repokit themes
+```
+
+<img src="media/list-themes.webp" width="100%" alt="listing-themes" />
+
 ## Motivation
 
 I worked in a codebase at Google that used just about every programming language in existence. Each team had their own methodology for exposing commands, scripts, and API's for their team's day-to-day development needs.

package/installation/install.sh

@@ -1,4 +1,4 @@
-CURRENT_VERSION="3.0.0"
+CURRENT_VERSION="3.0.2"
 CWD=$(pwd)
 
 REPLACEMENT="/node_modules"

package/internals/logger/logger.rs

@@ -5,7 +5,6 @@ use std::sync::MutexGuard;
 
 use colored::{ColoredString, Colorize};
 
-use crate::repokit::interfaces::RepoKitConfig;
 use crate::themes::theme::Theme;
 use crate::themes::theme_registry::ThemeRegistry;
 
@@ -17,11 +16,8 @@ static THEMES: LazyLock<Mutex<ThemeRegistry>> = LazyLock::new(|| Mutex::new(Them
 pub struct Logger {}
 
 impl Logger {
-    pub fn configure(configuration: &RepoKitConfig) {
-        Logger::set_name(&configuration.project);
-        for theme in &configuration.themes {
-            Logger::with_registry(|mut registry| registry.register_user_theme(theme))
-        }
+    pub fn set_name(value: &str) {
+        *REGISTERED_NAME.lock().unwrap() = value.to_string();
     }
 
     pub fn info(message: &str) {
@@ -42,6 +38,16 @@ impl Logger {
         exit(0);
     }
 
+    pub fn list(items: &[&str], indentation: Option<i32>) {
+        Logger::with_surrounding_space(|| {
+            let mut pointer = 0;
+            for item in items {
+                println!("{}{}. {}", Logger::indent(indentation), pointer + 1, item);
+                pointer += 1
+            }
+        })
+    }
+
     pub fn space_around(message: &str) {
         println!("\n{}{}\n", Logger::info_prefix(), message);
     }
@@ -115,8 +121,4 @@ impl Logger {
             format!("{}: ", theme.error_prefix(&REGISTERED_NAME.lock().unwrap()))
         })
     }
-
-    fn set_name(value: &str) {
-        *REGISTERED_NAME.lock().unwrap() = value.to_string();
-    }
 }

package/internals/repokit/repokit.rs

@@ -23,7 +23,10 @@ pub struct RepoKit {
 
 impl RepoKit {
     pub fn new(root: String, configuration: RepoKitConfig) -> RepoKit {
-        Logger::configure(&configuration);
+        Logger::set_name(&configuration.project);
+        for theme in &configuration.themes {
+            Logger::with_registry(|mut registry| registry.register_user_theme(theme))
+        }
         let theme = InternalFileSystem::new(&root).read_theme_preference();
         Logger::with_registry(|mut registry| registry.set_theme(&root, &theme));
         RepoKit {

package/internals/themes/theme_registry.rs

@@ -46,6 +46,9 @@ impl ThemeRegistry {
     }
 
     pub fn register_user_theme(&mut self, theme: &RepoKitTheme) {
+        if self.themes.contains_key(&theme.name) {
+            self.on_naming_conflict(&theme.name);
+        }
         self.themes
             .insert(theme.name.clone(), Theme::from_configuration(theme));
     }
@@ -99,4 +102,24 @@ impl ThemeRegistry {
             highlightColor: None,
         })
     }
+
+    fn on_naming_conflict(&self, name: &str) {
+        if ThemeRegistry::built_in_color_schemes()
+            .1
+            .map(|t| t.0)
+            .contains(&name)
+        {
+            println!(
+                "{}: I've discovered a theme that conflicts with one of my iternals. Please rename your {} theme",
+                self.current_theme().error_prefix("RepoKit"),
+                self.current_theme().highlight(name)
+            )
+        } else {
+            println!(
+                "{}: I've discovered two themes with the name {}. Please rename one of them",
+                self.current_theme().error_prefix("RepoKit"),
+                self.current_theme().highlight(name)
+            )
+        }
+    }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@repokit/core",
-  "version": "3.0.0",
+  "version": "3.0.2",
   "description": "A knowledgebase for your repository - wrapped in a CLI",
   "keywords": [
     "cli",