Feature/sample backend communication #12
Merged
Conversation
This file contains 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
oktaal
approved these changes
Nov 14, 2019
|
Thanks! As I tried to explain in #12, I stopped implementing a simple backend app because it felt so wrong. But perhaps, I'm thinking now, I could base it on the Django tutorial. Let me give it another try... |
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.
@oktaal: could you please have a look if this is ok? As I explain in #11, I only implemented the services at the frontend, because a fake app at the backend would really set a wrong example. Please let me know if the http handling should be done differently, because I expect, given this code, hardly anyone will change the backend calls (and they shouldn't have to).
This also enables live reload, which works like a charm on my machine 😉. Can you agree with that?