Standardize backend/frontend compatibility #29
Description
Wondering if we should:
- Automatically try to build the frontend when merging the backend to spot potential typing errors in the frontend triggered by schema changes
- Have an incremental version number in the open api spec?
- Maybe even get the node in the equation
The overall idea is to maintain compatibility between the different moving pieces of the explorer.