Experiment: migrate to DRF + React #228
Draft
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.
Status as of 01/05/2025:
/api/to the DRF routes to maintain functionality in the preexisting routes and try to move incrementally without breaking changes.api/explore/<model>/<id>works.api/explore/<model>/<id>/downloaddoes not work yet.api/page/<name>works.api/searchworks.api/export/<model>/<id>/formatdoes not work.api/site-infoworks.api/csrfworks./explorepage needs to be behind auth.Lots more to do if we want to move forward with this! I'm not 100% sold on this being the best use case for the frontend given all of the work to get credentials and make sure everything is secure. I am interested in trying Alpine.js and HTMX as a more lightweight alternative to React with the goal of phasing out Knockout and jQuery.