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

feat(participants): Allow teams in participants table #4022

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

iMarbot
Copy link
Collaborator

@iMarbot iMarbot commented Feb 22, 2024

Summary

Want to be able to use this table for teams too as it's compact and handy for displaying lists of teams that are participating (sometimes grouped) without needing to fill out team cards that have specific seeding assigned to them.

hjpa suggested disable storage for teams, but actually it would be useful to have it working for there too for the reason I mentioned above. Can still manually disable it if not used strictly for creating LPDB placements.

image

(sorry for awful screenshot, W11 HDR 👍 )

How did you test this change?

/dev on https://liquipedia.net/counterstrike/index.php?title=Test&oldid=2704673

Copy link
Collaborator

@hjpalpha hjpalpha left a comment

Choose a reason for hiding this comment

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

lgtm if tested
please also test on sc2/sc/wc/stormgate due to /custom being used there

@iMarbot
Copy link
Collaborator Author

iMarbot commented Feb 22, 2024

lgtm if tested please also test on sc2/sc/wc/stormgate due to /custom being used there

Those 3 override readEntry() with their own function which still has the assert on not being team opponents. I can change it there too if you want, but right now they should continue to function as they have been previously.

@hjpalpha
Copy link
Collaborator

lgtm if tested please also test on sc2/sc/wc/stormgate due to /custom being used there

Those 3 override readEntry() with their own function which still has the assert on not being team opponents. I can change it there too if you want, but right now they should continue to function as they have been previously.

imo if we allow it on commons we should allow it on the customs too

@Rathoz
Copy link
Collaborator

Rathoz commented Feb 23, 2024

I'm skeptical, this would have significant impact on the functioning on player's of the team in other places. Such as earnings of player, player results, player matches, upcoming matches of player, upcoming tournaments of player.

@iMarbot
Copy link
Collaborator Author

iMarbot commented Feb 23, 2024

I'm skeptical, this would have significant impact on the functioning on player's of the team in other places. Such as earnings of player, player results, player matches, upcoming matches of player, upcoming tournaments of player.

As I explained, this is not intended for permanent use on tournament pages. It's for temporary use where teams cannot yet be placed in teamcards for whatever reason.

The only one of those actually affected would be upcoming tournaments of player, something which few wikis support currently. And again, it would only be until team cards are possible to be filled out.

Also just want to be able to use the functionality of a wikitable that fills out with teams split into sections without storage too.

@iMarbot
Copy link
Collaborator Author

iMarbot commented Feb 26, 2024

Pushed change to all the customs and added fallback to not index entries table by nil when team template for the opponent doesn't exist and hence no name field.

Mixing players and teams on the custom wikis does disable the race columns, but I assume that's desirable behaviour?

image

@iMarbot iMarbot requested a review from hjpalpha February 26, 2024 20:19
@hjpalpha
Copy link
Collaborator

Pushed change to all the customs and added fallback to not index entries table by nil when team template for the opponent doesn't exist and hence no name field.

hmm, not sure we should do that
personally i always let it error with an error that says it doesn't exist
but not super important imo

Mixing players and teams on the custom wikis does disable the race columns, but I assume that's desirable behaviour?

image

yes that is intended faction/race columns disapear once you have mixed opponent types
they also disapear once you have a duo/trio/quad/archon opponent listed

@iMarbot
Copy link
Collaborator Author

iMarbot commented Feb 27, 2024

hmm, not sure we should do that
personally i always let it error with an error that says it doesn't exist
but not super important imo

image

image

Easier for casual users to understand what broken with the first one. Sure, we can add error message explaining more in the second, but we do the same on brackets where we don't break display for a missing TT.

image

@iMarbot
Copy link
Collaborator Author

iMarbot commented Nov 22, 2024

@Rathoz Any concerns with this still, or?

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