-
-
Notifications
You must be signed in to change notification settings - Fork 297
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
Generate traitnames and targets lists consistently #3114
Comments
Why do you want them sorted? FYI, traits are stored in a HashMap which are guaranteed to have inconsistent iteration order for this reason. |
I want to compare file content on two nominally identical servers to ensure that they are in fact identical. To do that a present is a multi-step visual process. Out of 160 plugins I test, the only content that isn't identical on server shutdown/restart is I understand that a HashMap can be sorted for output by converting to a TreeMap. If you are willing to accept a PR, I can pay my programmer to make it so, or I can contribute equivalent support to Citizens if you want to do it yourself. I appreciate that this is a relatively small thing that you might be unwilling to accept. |
Why not just make a script to compare yaml files? Should be trivial. |
I have done, for 10 years now. The script would be even more trivial if the lists were sorted. Thus the request. |
I don't think I can sort every single key in the saves.yml file, so better to update your script sorry |
If we post a PR to sort the three keys that we referenced above, will you accept it? |
No |
I confirm that I have ...
Description
saves.yml
files generate seemingly random order for traitnames and targets values. It would be nice for my purposes if the lists were consistent. I assume that it would be relatively straightforward to sort these lists alphabetically withCollections.sort()
or similar.Following is a difference example from two of the servers. Obviously, the targets lists are preceded by
and
respectively.
Code Example
No response
The text was updated successfully, but these errors were encountered: