fix for specs_v1.json compatibility with system #82
Conversation
…d specs.json, similar to load block features
|
|
| } | ||
|
|
||
| //call function to process core block directory | ||
| processCoreBlockDirectory(coreBlockDir); |
There was a problem hiding this comment.
Instead of doing this here I think we should check during the load process for this name and if it's specs_v1.json we should modify the filename and save it as specs.json, that way we would handle older block versions that may not be part of the core/blocks library
There was a problem hiding this comment.
Ok, I'll work on that, I did it this way, because this is similar to how it is handled using the load block button from the dropdown menu.
There was a problem hiding this comment.
I agree. Instead of converting the spec files when the app start, we can just try to load both specs_v1.json and specs.json when something tries to access the specs for block in the readSpecs function.
… file from specs_v1.json to specs.json
… file from specs_v1.json to specs.json
This fix closes #77
Creates a replicated version of specs_v1.json, and calls it specs.json for the system to recognize the proper file in dir.