What is the best strategy for importing JSON files containing component attributes (dimensions, location of drilling holes, material etc).
Is it better to:
Import one ‘large’ JSON file (it is not huge, about 40kb), filter it inside my definition to just the components I am interested in, and throw away the rest?
Have several smaller JSON files, maybe one of each type of attribute? This would mean I would need to do multiple imports and have more logic around deciding what I need to import.
At the moment I am doing option 1. My model is slow, and I think this import is the main driver of the refresh speed. It looks like the external file is being polled every time the configuration changes.
Is there a way to stop it polling after the initial import? I cannot use the toggle + stream filter technique to turn off the ShapeDiverTextInput component after importing the JSON - because then my definition is flooded with nulls as the input data is cut off.
Is there a better way?
[If it helps to look at the model, it is the only one in the anysizeflatpack account]