Per-entity game-patch history in the Version history sections - #812
Open
ptrlrd wants to merge 1 commit into
Open
Per-entity game-patch history in the Version history sections#812ptrlrd wants to merge 1 commit into
ptrlrd wants to merge 1 commit into
Conversation
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.
The Version history section on entity pages showed site-changelog diffs rather than the entity's actual balance history; I now maintain real per-patch histories in data/entity_history.json (811 entities across cards, relics, monsters, encounters, and events; refresh via tools/entity_history_sync.py), serve them at /api/update-history/{type}/{id}, and render them on every detail page with a fallback to the old timeline where nothing is recorded. Covers the version-history item in #795.