-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(match2): valorant participant issue in legacy #4754
Conversation
Can it really have gaps if it's being build with Array.extractValues? Or are you referring to potential other sources than the one introduced with the preceding PR? |
The one in from recordFromGame is using extractValues. hjp is talking about the one now built in MatchGroupInput/Custom. Which could allow for gaps (it either needs gaps or force empty tables at certain participants) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Summary
Allow
game.opponents
as an input format, which is automatically remapped intogame.participants
for storage.This allows access to
game.opponents
in Match/Legacy, just like in MatchSummary.How did you test this change?
/dev