Repository navigation
Show live incursion status on the Incursion page - #43
Merged
Merged
Conversation
Signed-off-by: Yoenis Hernandez <40134268+Fazorath@users.noreply.github.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
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.
Closes #23
Adds a "Live incursions" panel to the Incursion page's start screen. It reads ESI's public
/incursionsendpoint, so no sign-in is needed, and shows each incursion's state (established / mobilizing / withdrawing), constellation, staging system, infested systems, influence and boss. Constellation and system names come from the public/universeendpoints and fall back to IDs if they can't be read. It refreshes every 5 minutes (the ESI cache lifetime) and has a Refresh button.Tests:
test_incursions.py(5 new, passing). The GUI test files segfault under headless Tk in my environment (they also do on an untouched checkout), so the panel itself was only syntax-checked, not run; please eyeball it in the app.