-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix libcal booking #247
Fix libcal booking #247
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LOL good stuff thanks vincent!
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #247 +/- ##
=======================================
Coverage 91.38% 91.39%
=======================================
Files 59 59
Lines 2496 2510 +14
=======================================
+ Hits 2281 2294 +13
- Misses 215 216 +1 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One quick question before push
in_use = models.BooleanField(default=True) | ||
|
||
objects = GSRManager() | ||
all_objects = models.Manager() # for admin page |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that is great, thanks vincent! @tuneerroy @ashleyzhang01 @JeffersonDing @dr-Jess just for reference look at this man!
self.assertEquals(6, len(res_json[0])) | ||
self.assertEquals(6, len(res_json[1])) | ||
self.assertEquals(7, len(res_json[0])) | ||
self.assertEquals(7, len(res_json[1])) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'm imagining that the extra field is the in_use
? any reason it still shows up in the route despite all of our queries using .object
to query? if this is the case, I think we should remove this field from showing up
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh the serializer was still serializing all the fields. fixed now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bet LGTM
No description provided.