Repository navigation
fix(display): use configurable notification names - #211
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Visible strategy/account names drifted between the QRS catalog and notification renderers. Use a fixed mapping generated from the existing public catalog plus independent display aliases, with QSL_DISPLAY_NAMES_JSON overrides (VITE_QSL_DISPLAY_NAMES_JSON for console builds). Known names take precedence; unknown profiles retain a fallback. No origin month is invented for historical labels.
Trading/account/profile IDs, request/routing keys, fingerprints, release/continuity bindings, Secret/storage/claim/dedup keys, risk values, pins and lockfiles remain unchanged. No deploy, real notification, trading, IAM or Secret operation. Push/workflow_run/reusable-workflow triggers were audited; these changes trigger checks only.
Validation: mapping/locale/unknown-name/unchanged-input regressions, existing notification tests and current-head remote CI. QRS also builds the frontend, checks generated assets and validates original selection/operation requests. Local QPK float-bit and LongBridge editable-package VCS metadata limits are reported separately; no protection was relaxed. Refresh/check instructions: docs/display-names.md.