List anything that went well in this sprint including shout out to others that went out of their way to help (add your name after your comment)
Communication and collaboration. Especially between the frontend members (Mattu, Alec (NIH/NCI) [C])
I think our collaboration was especially good in this sprint. Everything seemed to go smoothly when it involved multiple team members working together to complete tickets. (Mueller, Austin (NIH/NCI) [C] )
We successfully (for the most part) met feature complete date! Kudos to the FE team! (Ying, Ming (NIH/NCI) [C] )
Testing team for identifying defects and easy configuration of the bento-core components (Rana, Ambar (NIH/NCI) [C] )
Communication with the team in regards to issues could be improved and we can be more proactive in taking steps to resolve them sooner(Mueller, Austin (NIH/NCI) [C] )
FE Refactor planning can be better. Only recently, we found some things that need to be moved/cleaned up. Luckily those are not big ticket items. We'll try to do better next time. (Ying, Ming (NIH/NCI) [C] )
What you have learned?
List anything you learned about in this sprint (add your name after your comment)
Building components somewhat dynamically based on props (e.g. different input types) (Mattu, Alec (NIH/NCI) [C])
I relearned to not take error messages at it's face value. There was an React error blocked me for a while, until Rana, Ambar (NIH/NCI) [C] helped me found the issue. It was somehow related to the error message, but nowhere close to the place the error message pointed to! (Ying, Ming (NIH/NCI) [C] )
Learned how to write NPX script that generates boilerplate code for Bento Reference Implementation like React CRA( Create React App) (Sheth, Karan (NIH/NCI) [C])