Open tosaddler opened 1 month ago
Thanks @tosaddler for noticing, will fix!
Seems like it may be re-appearing. Will take a deeper look later.
I can make a manual fix for this but would have to write it in.
FWIW, this is caused by extracting it out their their config.json file. I think it's a bug on their part. We can either provide some code to override the extraction or we can leave it.
Thoughts @KennethEnevoldsen?
Ahh that is frustrating - I would probably create an overwrite on our end (create some sort of file which takes priority).
Not sure where the info is pulled from, but it is showing
131072
rather than32768
.