CLI: expose public search language with --language

Open Beginner friendly
#88 1 comment 0 reactions 0 assignees View on GitHub

@semajzandrews is already working on this.

Since Nov 14, 2026.

  • #89 by @HarshRajSinghania — closed without merging

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
cli, python
Domain
cli

Research direction

The change belongs in spotapi/cli.py, where the search subcommand's arguments are defined and forwarded to Public.search; tests/test_cli.py is where the offline cases go. Read how the existing search arguments are wired, then add an optional --language flag and pass its value through unchanged. Done means the help text shows an example locale, omitting the flag behaves as before, and offline tests cover both supplied and omitted cases.

Written by the indexing model from the issue text.

Description

enhancement good first issue

Problem

Public.search(..., language="fr-CA") already supports localized public search, but spotapi search does not expose that option. CLI users must write Python for a capability the CLI can forward directly.

Proposed change

Add an optional locale flag:

spotapi search "Charlotte Cardin" --language fr-CA

Pass its value unchanged to Public.search(..., language=args.language).

Acceptance criteria

  • spotapi search --help documents --language with an example locale.
  • Omitting the option preserves current behavior.
  • The supplied value is forwarded unchanged to Public.search.
  • Offline tests cover both the supplied and omitted cases.
  • No new dependency or Spotify endpoint is introduced.

Scope

The likely implementation is limited to spotapi/cli.py and tests/test_cli.py. Do not add automatic locale detection or change the Python API as part of this issue.

Comment before starting so duplicate work can be avoided.

Dominant language
Python
Stars
493
Forks
40
Avg merge
5m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Aran404/SpotAPI

All issues in Aran404/SpotAPI

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.