Skip to content

Alarm cards do not say what a rule does, and Poracle can tell us #810

Description

@hokiepokedad2

v2 tracking reads take ?include_descriptions=true and return a human-readable sentence for every rule, rendered by PoracleNG in the user's own language. We already pass includeDescriptions=true on one v1 call (/api/tracking/allProfiles) and use none of it.

Our alarm cards describe a rule with filter pills — IV, CP, level, PVP, gender. They are compact and they are good at comparison, but they do not say what a rule does, and a rule with an unusual combination of filters is genuinely hard to read off them. Poracle's own sentence is the same text the bot shows, which means the two surfaces would finally agree.

What to build

  • Carry the description through the v2 read path onto the alarm models.
  • Put it on the card. Not instead of the pills — they earn their place when scanning a list of forty rules — but as the line that answers "what is this one". Work out which reads first.
  • It is localized by PoracleNG using the alert language, and our pills follow the display language. Those can differ. Decide which this follows and be consistent, rather than letting a card mix two languages.
  • Long descriptions need a truncation rule that does not turn every card into a paragraph.
  • Capability-gated: no descriptions, no line, and the pills carry on alone.

Depends on

The v2 pilot. This lands on whichever types have moved to v2, starting with pokemon.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions