Use schemas RPC APIs in the front end on the database page #3648
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Notes
This PR implements the front end side of our RPC refactor for the following REST endpoints:
/api/db/v0/schemas/{schemaId}/
schemas.delete
/api/db/v0/schemas/{schemaId}/
schemas.patch
/api/db/v0/schemas/
schemas.list
/api/db/v0/schemas/
schemas.add
Working functionality
Notable user-facing changes
Exploration counts are removed from each schema card
We discussed this previously and made this choice in order to simplify implementation.
Broken functionality
Basically every other page of Mathesar is broken except for the root page which shows connections.
For example, the schema page looks like this:
Checklist
Update index.md
).develop
branch of the repositoryDeveloper Certificate of Origin
Developer Certificate of Origin