add support for jobs end point #135
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The concept of Jobs does not exist in self-hosted parse-server (jobs was always a hacky workaround anyway), so does it make sense to support this feature of parse that will disappear in a few months? |
|
While I'm inclined to agree with Miles, I don't see a downside to accepting the pull request as is (and dropping it once Parse.com shuts down). Does anyone else see a downside? |
|
agreed with @danrobinson -- this won't break anything |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
jobs endpoint is similar to functions end point. it would be nice to have it supported as well.