-
Notifications
You must be signed in to change notification settings - Fork 240
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
Refactor ModalBase from existing modals #595
Conversation
ModalBase can accept an imageModal prop to change behavior and match existing functionality.
✅ Deploy Preview for activist-org ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Thank you for the pull request!The activist team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :) If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Development rooms once you're in. It'd be great to have you! Maintainer checklist
|
Thanks @anthonyshibitov! I'll check this in the coming days and provide some feedback 😊 |
Looking good so far, @anthonyshibitov! I'm going to wait on #565 to get merged before bringing this in. Some thoughts on this:
|
DialogTitle is now defined in the modal component
Alrighty, looks like I've got points 2 and 3 all set 😎 I'm not sure what you mean by removing the active state from the image though, could you explain that? |
Remove unused props variable
I can take a look at it myself, but when I click the image to close it there's a border that appears around it, whereas when we'd click the sides there wouldn't be. Trying to make sure that the closing modal experience is the same :) |
Are we good for a final review on this, @anthonyshibitov? :) |
yessir! |
Wunderbar 😊 I'll get to it soon then :) |
</div> | ||
</Dialog> | ||
<ModalBase imageModal> | ||
<template #normalDisplay> |
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.
This is some great stuff here, @anthonyshibitov :)
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.
Really well organized. The double multiple slots that are named makes this super easy to follow 😊
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.
Thanks for this, @anthonyshibitov! I'll try to play around to get the image boundaries to be clickable to close it :)
Refactor ModalBase from existing modals
ModalBase can accept an imageModal prop to change behavior and match existing functionality.
Contributor checklist
Description
Refactor modal functionality to a separate
ModalBase.vue
component.imageBase
can be added to the<ModalBase>
component to mimic the functionality we currently have, where images and text modals behave (click image to close modal) and display (text modal has close button and title in a card, with the content within it) differently.Note that this currently does not support i8n in the modal title (specifically,
{{ $t("components.modal-qr-code.header") }}
). I wanted to get some feedback on this before fleshing out the remaining portions, to make sure this design is what we're looking for. Let me know if this is okay, and I will commit another change to try and fix the i8n issue (I'm currently not sure how to do this, any ideas would be great lol 😀). If we want the modal to behave differently, I'll go back to the drawing board.Also, note to myself, the bug where clicking to the left or right of the image modal does not close the modal still exists 🙃
Related issue