-
Notifications
You must be signed in to change notification settings - Fork 27
remove pointless data transformation. #8960
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
Conversation
✅ Deploy Preview for ilios-frontend ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
this doesn't do anything meaningful and gets in the way of using a more robust data structure, like a class with getters or a Proxy object. begone!
e781862 to
4db5d76
Compare
|
My only concern is the |
this has to do with displaying multiple events as one in the weekly and monthly calendar. if it's a multi-event, clicking on it will take you to the calendar's day-view with all similar events expanded. |
|
@dartajax - for testing purposes - this change affects the dashboard calendar only. regression testing should focus on events on the week- and month-view that expand to multiples in the day-view when clicked upon. no functional changes are expected, this should work as before. |
dartajax
left a comment
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.
click-tested per instructions from @stopfstedt - seems fine - no changes noticed on Dashboard calendar - clicking into multiples from Week or Month view - behaves as before so ... approval granted
this doesn't do anything meaningful and gets in the way of using a more robust data structure, like a class with getters or a Proxy object. begone!
extracted from #8956
side-note
further down, we're modifying the events by setting a
isMultiflag if applicable. i believe that the removed code is related to that, although i can't back that claim up based on commit messages.ideally, we'd not be modifying these events at all, once they're generated. conceptually, they are "read only".
will explore a solution that gets rid of a
event.isMultias a separate issue.