In the last PR we chagned one of the schema but the script to update the schema wasn't run. We need to run the script to update the schema.
Maybe we can run a jop that will automatically run the script when a PR is merged to update the schema, but in this case we can not validate the schema in advance since the new resource is not in the list. So the new approach would be:
People can add a new schema, the existing validator will only throw a warning if the schema is not in the list, but will not end the process. This makes it easier for people to handle the data since they do not need to install the node dependencies to run the script to update the schema. The script will be run automatically when a PR is merged, if there is a new entry for the schema, a PR will be created to update the schema file (if this is possible)
In the last PR we chagned one of the schema but the script to update the schema wasn't run. We need to run the script to update the schema. Maybe we can run a jop that will automatically run the script when a PR is merged to update the schema, but in this case we can not validate the schema in advance since the new resource is not in the list. So the new approach would be: People can add a new schema, the existing validator will only throw a warning if the schema is not in the list, but will not end the process. This makes it easier for people to handle the data since they do not need to install the node dependencies to run the script to update the schema. The script will be run automatically when a PR is merged, if there is a new entry for the schema, a PR will be created to update the schema file (if this is possible)