Closed trullock closed 3 years ago
The board has a reference to its core which has a collection of boards. It's harmless if a bit wasteful. To prevent it you would have to make a new object and copy just the necessary properties, and then serialise that. Let's not complicate the code for a minor efficiency until we run out of serious issues.
I agree this isnt a high priority, and I understand how the serialization as led to this, but settings.json
should contain settings. This info isnt a setting, but because its in settings it looks like a setting, which is bad.
What do you propose then? I argue that the board selection is a workspace setting — this project targets that board. I would accept the proposition that FQBN fully identifies the selection. I was just being lazy storing the whole damn object,
Yea just trim the object and only store what's needed, is that just the fqbn?
Just my $0.02...this doesn't have any impact of the memory space used on the controllers, does it? If not, then I don't care what the settings.json file contains...
No effect at all on the Arduino binary.
I chose a board, my
settings.json
now contains:Doesnt seem desireable