Frontend blocks #8
Open
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
We may want to add a "Save" or "Submit" button, or we may just want it to always auto-save. For now, it submits every time $scope.schedule updates.
|
oh, and I'm hard-coding the schedule ID for now - until we set up some kind of login system or something, we're only going to be supporting one schedule. You'll want to add "SCHEDULE_ID=1" to your .env |
|
#7 has the PUT stuff in it. Imma take a look at the stuff today. Overall it seems to be aight. |
There was a problem hiding this comment.
👍 good expressive use of lo-dash
|
👍 lookin' good my friend! |
|
That is pretty sick. I like that angular-drop |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I think I've got the front-end mostly set up to handle schedule blocks and update them accordingly when the user interacts with the UI. I'm having some trouble with the schedule API calls, though: I'm not sure how to make GET give me each block's teacher and student group IDs, and when I PUT a new schedule, it says 200 but doesn't seem to actually update the schedule on the server. Ideally I'd like to spend some time digging into these for my own edification, but for now: any tips from our Ruby guys?