fix preferential gauges #95
Merged
Conversation
This file contains 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.
Fixes #94
When we first introduced the preferential gauge concept, the only way for a gauge to be preferential on L1 was by being added to the
GaugeController. This changed with theEventEmitterand now it's possible that a gauge added to theGaugeControlleris already the preferential one.This PR fixes this edge-case where a gauge was the preferential but had the
isPreferentialGaugeattribute set tofalse--handleNewGaugeused to always set that param tofalsefor the preferential gauge before the event was emitted, but in this case the old and new preferential gauges are the same.