Evaluate which short codes and abbreviations to keep

Open
#437 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
api, backend

Research direction

Start by comparing the V2 data structures for card cycles and card sets with faction handling in the NRDB Classic Search, especially its special - faction shortcode. Decide which legacy short codes and abbreviations should be supported, then identify where V2 parses and exposes those values. Done means documenting the chosen codes and adding support for them, including faction codes where needed.

Written by the indexing model from the issue text.

Description

Some V2 data structures have legacy short codes available, like card cycles and card sets . factions do not, but the NRDB Classic Search does support shortcodes for the factions, including a magical - value that i only learned about recently. :)

Where we have the legacy codes available, we should probably allow them to work.

Where we don't have them yet we probably want to add them.

Dominant language
Ruby
Stars
10
Forks
9
Avg merge
2h 59m
Merged PRs (30d)
2

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 Null-Signal-Games/netrunnerdb-api-server

All issues in Null-Signal-Games/netrunnerdb-api-server

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.