WPI: Initial setup of React in Django #10
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lpatmo
changed the title
|
I think this should be in a separate repository, as it is still coupling the frontend code with the backend service. |
|
Basically, as long as all of the prototype backends adhere to the API specification, they can be developed independently of the backend code. This allows for experimenting with different client frameworks, like Vue or Flutter. |
|
Sounds good! This PR was based off of a particular Django+React pattern I found, but decoupling the front-end completely makes sense too. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a WIP from the 40-minute stream at https://www.twitch.tv/videos/483344260
[ ] Is this the pattern we want to go with? An alternative is to separate the front-end entirely.
[ ] Make sure that this implementation works