Improve alerts of password reset #70
Comments
|
hi, I am interested in working on this issue. Though I am new, I have already worked on #1725 and have gotten some familiarity with the process. |
|
@alayek you're on! Looking forward to the PR. |
|
Before that @Sing-Li, I would like to get some clarity on the issue, since this is lacking description in detail. For the moment, we are resetting password by going to Are we planning to replace this Toast, with some password change specific code? Like Password Reset Successfully ? Or would we want more, such as on reset password logout the user and ask the user to login again? Or do we add an email confirmation, with text like Someone just reset the password and a recovery link? |
|
@engelgabriel which ones you mean? The toasts in the password reset by email and by settings looks pretty decent to me |
|
Hi, I'd like to try to work on this issue as part of hacktoberfest but I'm not really sure what the issue is meant to address. The above comments indicate to me that there might not be that much left to do. |
|
I would like to take this up. ✋ |
* Initial commit for newsfeed * Create server setting for Newsfeed * Solve linting * Callback for initializing and deinitializing newsfeed * Solve liniting * Access all users in initialize function * Check if newsfeed for a user already exists * Partial progress upload Declaring Newsfeed URL Declaring Newsfeed as new roomType Displaying the correct Newsfeed for the owner * Add deinitialize newsfeed function * set newsfeed_enabled default as false * Delete createNewsfeed.js * Delete createNewsfeed.graphqls * Delete newsfeed.graphql * Delete no-use file created by me * Display newsfeed channel name as Newsfeed in UI * Create Newsfeed when a new user registers on the server * Newsfeed creation using username instead of name * Few Improvement: -Change newsfeed icon to star -change channel type to n in canSendMessage function * Initial commit for follow user and follow button * Initialize follow user method * Follow Meteor method initialized * Follwers and following update in database and creation of toastr * solve linting * Change follow button to unfollow if already followed * Create unfollow user method * Update followUser method to store followers as object with _id as the key * Update hasAlreadyFollowed method in respond to change in storage scheme * Update unfollowUser to new scheme * Add to deInitialize newsfeed to remove following and followers from database * based newsfeed type room on private group * Mid progress for displaying messages in newsfeed * Publish followers and following from server to client * Relaying of first messge successful * Relay of first message * Solve linting * partial improvements * Revert "Solve linting" This reverts commit 14d4a73. * Revert "partial improvements" This reverts commit 1bcc673. * Solve linting * Partial progress with bug and without lint * Relay with identified bug * getLastMessage method added * Add getFollowers and getFollowing method * Display of original channel name in newsfeed * Revert "Display of original channel name in newsfeed" This reverts commit b94ae9c. * Add posted_in in front of sender in newsfeed * Change isSequential for newsfeed * Update followUser method to new schema * Update hasAlreadyFollowed for new schema * Update unfollowUser method to new schema * Update getFollowers to new schema * Update getFollowing and getFollowers * removed test code * Mid progress to new schema * remove default user fields in accordance with new schema * Migrate ChatMessage UI to new schema * Only rooms which can be viewed by user can show messages in newsfeed * Partial progress * Crude time and channel based summarization system for newsfeed * Eslint fix * seperation of summarization * Referesh in follow/unfollow button state * summarization on client for newsfeed
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: