Skip to content
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

add browser based notifications #69

Merged
merged 1 commit into from
Dec 22, 2017
Merged

add browser based notifications #69

merged 1 commit into from
Dec 22, 2017

Conversation

pranay414
Copy link
Collaborator

Added browser based notifications on successful file upload

Fixes issue #38

@ghost ghost assigned pranay414 Dec 21, 2017
@ghost ghost added the in progress label Dec 21, 2017
@NITDgpOS NITDgpOS deleted a comment Dec 21, 2017
@NITDgpOS NITDgpOS deleted a comment Dec 21, 2017
@NITDgpOS NITDgpOS deleted a comment Dec 21, 2017
@NITDgpOS NITDgpOS deleted a comment Dec 21, 2017
@NITDgpOS NITDgpOS deleted a comment Dec 21, 2017
@NITDgpOS NITDgpOS deleted a comment Dec 21, 2017
@NITDgpOS NITDgpOS deleted a comment Dec 21, 2017
@@ -3,6 +3,8 @@ import DropzoneComponent from 'react-dropzone-component';
import FilesActions from './../actions/FilesActions';
import PropTypes from 'prop-types';

Notification.requestPermission();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The request for permission should be done in the constructor. Also, if the user has already rejected the permission, stop bugging him/her again.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there any advantage in doing so?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We shouldn't write arbitrary code outside the react components. It is error-prone. It should be a part of the component life-cycle.

@nkprince007
Copy link
Member

@gitmate-bot rebase

@nkprince007
Copy link
Member

Hey! I'm GitMate.io! This pull request is being rebased automatically. Please DO NOT push while rebase is in progress or your changes would be lost permanently ⚠️

@nkprince007
Copy link
Member

Automated rebase with GitMate.io was successful! 🎉

@nkprince007
Copy link
Member

unack 1d40d26

Please address the requested changes. @pranay414

@pranay414
Copy link
Collaborator Author

@nkprince007 I am not clear on what you mean by unack 1d40d26, can you explain it?

@nkprince007
Copy link
Member

nkprince007 commented Dec 22, 2017

Uhm, that's a part of GitMate.io application, that allows me to accept and reject commits with the commands ack and unack. You don't need to worry about that. Once I'm happy, I'll be ack or acknowledging your commits.

And the bot is using my-account to post comments. So, it may seem like that I'm doing so, but it is infact a bot.

Added browser based notifications on successful file upload

Fixes issue #38
@nkprince007
Copy link
Member

@gitmate-bot rebase.

@nkprince007
Copy link
Member

Hey! I'm GitMate.io! This pull request is being rebased automatically. Please DO NOT push while rebase is in progress or your changes would be lost permanently ⚠️

@nkprince007
Copy link
Member

Automated rebase with GitMate.io was successful! 🎉

@nkprince007
Copy link
Member

Never merge master into your branches. We do not want merge commits. They mess up history. Refer https://coala.io/rebase for more info.

I've rebased your PR with GitMate for now. But make sure you stick to that philosophy. Because most of the git based projects prefer linear commit history.

Thanks for the PR, By the way 🎉

@nkprince007
Copy link
Member

ack c54f575

@nkprince007 nkprince007 merged commit beff086 into NITDgpOS:master Dec 22, 2017
@pranay414 pranay414 deleted the feature/browser-notifications branch December 22, 2017 08:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants