SetYaml
- 6 Devlogs
- 10 Total hours
pretty much just added a check for when the user tries to create a new object when he already has created one.
also removed a few debug stuff and added some TODOs
the user can receive the list of changes in the configuration and handle it as soon as it arrives, without to make the software detect the change (with polling for example)
about the other changes, I was creating an instance of the configuration object every time the file was changed, which does not help performance at all. Now I just update the one we already have.
I faced a LOT of errors while coding that.
last devlog I had pretty much all the idea of how I wanted it to be but it wasn’t implemented at all, so I started changing whatever I needed in the code for it to work (such as creating parsing methods, ways to bump Java field’s values into the yml, etc).
now it pretty much works, but I haven’t tried creating dynamic variables of more complex types and I also don’t have a smart way to update THE FILE whenever the user updates the variable, instead of the way around which already works.
with pretty much one line of code, you can receive an object of your choice that is binded to a file also of your choice.
whatever you change in the file will reflect in the object during runtime.
also, the file is created based on the model of the object’s class (which means you can define default)
pretty much just create whatever configuration you want, ask for an instance of it and the software will do the rest