Skip to content

inform of deprecation on parse-server #405

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

Closed
wants to merge 1 commit into from

Conversation

jaimeagudo
Copy link

Avoid newcomers wasting time implementing something useless
See parse-community/parse-server#3455

Avoid newcomers wasting time implementing something useless
See parse-community/parse-server#3455
@hramos
Copy link
Contributor

hramos commented Feb 3, 2017

Instead of adding a warning, let's remove the content that is no longer relevant on Parse Server.

The content on setting up push and using installations is still relevant regardless of whether clients can send pushes or not, so let's leave that in.

Can you update your PR to ensure only the outdated sections are removed? Ideally this PR would touch all other platforms as well as this is not iOS-specific.

@jaimeagudo
Copy link
Author

You are right but at the moment I don't have the time to go through this, but, IMHO is better to merge this and add a TODO than leaving it as it's

@hramos
Copy link
Contributor

hramos commented Apr 20, 2017

What I am advocating for is removing the stale content. I'd rather prune the no longer relevant sections and not add a warning. Seems like an equal amount of work for doing the right thing.

@TomWFox
Copy link
Contributor

TomWFox commented Mar 17, 2019

I'm closing this now as I have opened a PR which overhauls the push notifications section - #604.

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.

5 participants