Closed tooxo closed 3 weeks ago
@devgianlu I implemented the feature how I imagined it when I wrote the issue a few days ago. It would be great if you took a look at it if this works with your project. I have been testing my code for the last few days and didn't find any issues yet.
If you have questions, please ask or "review" the corresponding code parts.
Edit: While working on your code I noticed that you seem to split up your configuration structs to pass every field of the struct into a function. Is there a reason behind this? For me it seems like this just adds extra steps, when one wants to add a new configuration variable.
While working on your code I noticed that you seem to split up your configuration structs to pass every field of the struct into a function. Is there a reason behind this? For me it seems like this just adds extra steps, when one wants to add a new configuration variable.
Yes, that is not very wise or clean, but I think it should be sorted out in another PR.
I think it is now ready from my side, let me know what you think.
After this I think we're good to go, feel free to reword/reorganize the commits or I'll just squash this PR.
After this I think we're good to go, feel free to reword/reorganize the commits or I'll just squash this PR.
Just, squash it, should be alright.
This is a first POC for implementing the feature I mentioned in #36. I've never written any GO before, so it would be nice if someone could give me some feedback on where I could make improvements.
Features:
(The synchronization should only be enabled, if externalVolume is true)