-
Notifications
You must be signed in to change notification settings - Fork 53
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
Trip sharing #1304
Trip sharing #1304
Conversation
… planned by other
…e I'm a companion.
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.
Trip notifications are working for observers and dependents!
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.
Instead of passing the disabled
prop so many times, could we use a fieldset
and pass it once? https://www.w3schools.com/tags/att_fieldset_disabled.asp
Otherwise code looks good! Just a few suggestions.
@@ -639,6 +639,10 @@ components: | |||
tripNotAvailableOnDay: Trip not available on {repeatedDay} | |||
unsavedChangesExistingTrip: You haven't saved your trip yet. If you leave, changes will be lost. | |||
unsavedChangesNewTrip: You haven't saved your new trip yet. If you leave, it will be lost. | |||
TripCompanionsPane: |
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.
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.
It is indeed a separate issue, see #1331.
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.
Thoughts on adding an informational alert on this page if it's isReadOnly
letting users know why everything is disabled? We can use the Alert
component from building blocks. Happy to suggest some language if this is the direction we want to go in
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 do like the idea, looking at a banner that says " has added you to this trip. Therefore, you cannot make changes.". The Alert component in building-blocks is not quite usable for this purpose without restyling it (tricky to import, excess padding/margins even without the icon), so I'll use the react-bootstrap one for the time being.
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.
@amy-corson-ibigroup Let me know what you think of 5cc84f0.
if (isReadOnly) { | ||
return <MonitoredDays days={dayFieldsToArray(monitoredTrip)} /> | ||
} |
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.
Smart!
Good catch! Updated in bcba926. |
Good idea, addressed in 55ed3b7. |
Description
Works with ibi-group/otp-middleware#271, needs #1302.
This PR adds trip sharing in monitored trips: A user saving a trip (whether for themselves or a dependent) can assign confirmed companions as trip companions or observers. Someone assigned as a primary traveler, companion, or dependent has read-only access to the trip (they can view trip details but cannot make changes).
PR Checklist
Screenshot: