-
Notifications
You must be signed in to change notification settings - Fork 214
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
Add db import info for team/loadout/build #2145
Comments
I will work on it |
Actually, importing teams doesn't remove existing teams not in import. Even with the |
Seems so https://discord.com/channels/785153694478893126/1218906581593231540, tho i still feel like its weird that teams are not deleted with that setting enabled |
This thread has been marked as not a bug. So, this behavior shouldn't be changed ? |
Leaving @frzyc to give final say |
Yeah i do not think its worth any developer's time to dedup/merge team/loadouts. The ask for this issue is basically just add a tally as a visual for users, and not to add any complex logic to db |
There is already a dedup/merge for team and loadouts I think |
If no dedup/merge should be done, what will be written on the card ? |
Just the number of team/loadout/builds before import, and after |
Also TC Builds ? |
Yes, and TC builds |
How the total amout of loadouts can be computed ? |
yeah loadouts are called |
Thanks |
Currently only shows art/weapon/char
For importing GO data on another GO data for team/loadout, I believe the current logic is the import data overwrite the existing data. I think I am fine with that, deduping would be unnecessarily complicated, the UI should just reflect this.
The text was updated successfully, but these errors were encountered: