Replies: 2 comments 1 reply
-
Yea that is definitely one that I intend to do soon. The current config is actually already parsable so it shouldn't need to be json, i just havent taken the time to implement it yet. |
Beta Was this translation helpful? Give feedback.
1 reply
-
The feature is now in the latest beta, 2.10.0-Beta1 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Usually updating the YTSP config file is a pain in the ass due to it having to override. I had a suggestion of how we can avoid this issue
My idea is that you convert the current setting file into a JSON one to better file handling. And for updating you should get the current configs in the old config file and write a new one (but not overriding it) with the previous informations. So it would be in this way:
Imagine that we have those configs in the config file:
And that you wanna add a config called
New_Stuff
. What you could do is to make a simple setting getter that creates a value in the file and returns a default value if it does not existThis isn't perfect, since you lose your comments about the settings, but I guess this is worthy. For the comments, you could write in the wiki which setting does and which doesn't instead
Beta Was this translation helpful? Give feedback.
All reactions