Conversation
|
Looks good to me, code looks clean |
Roadlyfe
left a comment
There was a problem hiding this comment.
Code looks good and clean. nice work!
lisamdespain
left a comment
There was a problem hiding this comment.
Looks really good - you have a lot going on but you implemented it well.
| subject, | ||
| description, | ||
| course_name, | ||
| course_description, |
There was a problem hiding this comment.
I think at some point we need to address that times could be different on different days. Example: Monday class could start at 9am, but Tuesday, class starts at 3pm.
| { title: 'instructor', text: instructor_name }, | ||
| { title: 'class size', text: size }, | ||
| ]; | ||
| // const data = [ |
There was a problem hiding this comment.
Maybe ok to delete instead of commenting it out?
82685b7
reneetro
left a comment
There was a problem hiding this comment.
I agree the second set of data that is commented out in the ParentBookingCard.js can probably be removed. You may still want to have a key for each ParentBookCard (perhaps item.id?), that might not be necessary though. Everything else looks nice and organized, it would be awesome to have a Loom so we can see what it looks like!
DawsonReschke
left a comment
There was a problem hiding this comment.
Code look great, well written and clean. There was a large object that was commented out, perhaps remove that, otherwise good job!
Austin-T-Johnson
left a comment
There was a problem hiding this comment.
Great job overall, looks like there was a lot implemented on this ticket! I left a few notes in the files changed for your consideration!
|
|
||
| const BookingCalendar = () => { | ||
| const onPanelChange = (value, mode) => { | ||
| console.log(value.format('YYYY-MM-DD'), mode); |
There was a problem hiding this comment.
Wondering what this function is intended to do? Looks like currently, it is just console logging the date?
| ) | ||
| .post() | ||
| .then(res => console.log(res)) // TODO: Let's perform some action with this result. | ||
| .catch(err => console.log(`message: ${err.message}`)); |
There was a problem hiding this comment.
great job adding a catch to handle errors
| <Form className="il__top__form" size={'large'} layout="inline"> | ||
| <Input.Group | ||
| compact | ||
| // style={{ display: 'flex', flexDirection: 'column' }} |
There was a problem hiding this comment.
You might want to remove this commented out code
| > | ||
| <div> | ||
| <div | ||
| style={{ |
There was a problem hiding this comment.
You might want to consider adding the styling in a separate CSS file to clean up the code a bit
There was a problem hiding this comment.
Yes absolutely we were just doing this to prevent switching between screens so much. This is still a draft PR at this point! Thank you!
MaxT6
left a comment
There was a problem hiding this comment.
Nice job creating the form to search for courses. There is a chance to clean up the code but overall the code looks great!
| <ParentBookingCard key={idx} booking={item} /> | ||
| </div> | ||
| <div> */} | ||
| <ParentBookingCard booking={item} /> |
There was a problem hiding this comment.
Is there a reason this code is commented out?
src/styles/calendar.less
Outdated
| margin: 0 4%; | ||
| } | ||
| } | ||
| //Calendar Card for |
There was a problem hiding this comment.
I appreciate the label but what is the calendar card for?
| import axiosWithAuth from '../../../utils/axiosWithAuth'; | ||
| import { useOktaAuth } from '@okta/okta-react'; | ||
| import { addToCart } from '../../../redux/actions/parentActions'; | ||
| import { dummyData } from '../../../dummyData'; |
There was a problem hiding this comment.
Good job labeling your data as such to indicate it will need to change.
There was a problem hiding this comment.
I'd go one step further here and indicate. 'what kind of dummyData' it is. Example
dummyUserData etc.
| }} | ||
| > | ||
| <button | ||
| style={{ |
There was a problem hiding this comment.
Let's make these styles 'DRY' and not inline. :)
There was a problem hiding this comment.
Oh yes we plan to export the styles and make them DRY, we were just using everything inline to prevent switching between screens so much while implementing the figma design. We have actually switched to a dropdown on our current branch. We are implementing ant design styles as well! Thank you for your input Ryan!
ryan-hamblin
left a comment
There was a problem hiding this comment.
I noticed in ParentBookingChild that we're already customizing buttons using inline styles. Let's not do the styles inline, and I would heavily consider the use of AntD's buttons here. Always stick with the easiest path which in this case, is to use the built in library for styling. No need to reinvent button right?
1110bd1
AlexiusThomas
left a comment
There was a problem hiding this comment.
Great code but I definitely see the areas of improvement.
AlexiusThomas
left a comment
There was a problem hiding this comment.
i see that testing has started and all checks passed. That is good
Description
Created a form where parents can search for available courses when exploring programs for their children.
Co-Authors:
Fixes # (issue)
Loom Video
https://www.loom.com/share/c77e0d6d9b674ccab07514954b8235a6
Type of change
Checklist: