squashd / gogi

quick configurable .gitignore templates manager

👋 Hi, I'm Dan

🎾 Background: At university, I balanced studying mathematics with playing squash semi-competitively (hence the profile name), but I found that I like solving problems in code rather than on paper, so I've been all in on programming for the last few years.

👨‍💻 Coding Path: Learned the basics first with Python. Moved onto frontend where I discovered my problem-child, TypeScript. My first repo was a basic HTML page, but even that simple little thing struck a chord. Later, I shifted to backend, delving into C# and ASP.NET Core.

gogi's Issues

Test Suite Alters Local Config

Running the test suite modifies the local configuration files. Tests should not have any side effects on the development environment.

Steps to reproduce:

1. Run tests
2. Observe changes in local config files

Expected behavior: Local config remains unchanged after tests.

Allow Imports of .gitignore templates

Sometimes you find a nice gitignore or you have one ready you want easily accessible

Task:

• Allow for imports of gitignore files
• There should be no naming conflicts
• Optional flag to set as base

Implement Template Renaming Command

Need a quick way to rename templates. It's a hassle to do it manually.

• Add a rename command.
• Ensure it updates all references.
• Make it fail if the new name already exists.

Add Confirmation Prompts for Destructive Actions

To prevent accidental loss, introduce confirmation prompts for destructive actions.

• Implement prompts for delete and overwrite operations.
• Add a --force flag to bypass confirmation for experienced users.
• Include a setting to disable all prompts by default, set to false.

Objective: Balance safety with efficiency in tool operations.

force init or reset command

sometimes you just want to burn it all to the ground.

Set Editor Flag

Allowing for customizable initialization requires a rewrite of the go-config library.
Putting a pin in this here to remind me

Add First-Run Interactive Config Setup

Task: Code an interactive prompt for initial setup to capture user preferences like text editor choice. This should kick in on the first run or when a config file is missing.

• Check for config file on startup.
• If not found, launch setup prompts.
• Save preferences to a config file.
• Include a --config flag to reinitiate setup anytime.

Purpose: Skip the manual config edit and get straight to work.

Add Shortcut Flags for Commands

Enhance tool efficiency with flags for common template actions.

• -e: Edit a template immediately after creation.
• --set-editor: Set default editor during initial tool setup.
• -b: Mark a new template as the base template instantly.

Purpose: Simplify and accelerate template management.