Skip to content
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

Merged
merged 5 commits into from
Sep 17, 2024
Merged

Conversation

Rathoz
Copy link
Collaborator

@Rathoz Rathoz commented Sep 17, 2024

Summary

Allow game.opponents as an input format, which is automatically remapped into game.participants for storage.

This allows access to game.opponents in Match/Legacy, just like in MatchSummary.

How did you test this change?

/dev

@Rathoz Rathoz requested review from mbergen and hjpalpha September 17, 2024 13:33
@Rathoz Rathoz requested a review from hjpalpha September 17, 2024 13:56
@mbergen
Copy link
Collaborator

mbergen commented Sep 17, 2024

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?

@Rathoz
Copy link
Collaborator Author

Rathoz commented Sep 17, 2024

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)

Copy link
Collaborator

@mbergen mbergen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Rathoz Rathoz merged commit 6e44cab into main Sep 17, 2024
5 checks passed
@Rathoz Rathoz deleted the m2-game-opponent-legacy branch September 17, 2024 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants