AWS-WSU/warrior-bot

[FEAT] Refactor `wb where <location>` to use a more elegant solution

Open

#19 opened on Nov 20, 2025

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Python (0 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (2 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Is your feature request related to a problem? Please describe. Right now we're storing locations in a JSON file and parsing it to return the address/exact location which is fine but we'd ideally want something more elegant...

Describe the solution you'd like Relying on JSON is fine, the issue is getting the data. Feel free to be creative about this, there's no specific solution that we need.

For Developers- what would your solution be?

See above. Also keep in mind, if you are pursuing this, read #13 and reach out to @cachebag since that will no longer be relevant.

Additional context None.

Contributor guide

Research direction
Explore alternative data storage solutions for locations, considering scalability and maintainability.
Tech stack
python
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55