Skip to content

Makes sure routes don't overlap and yield a header set error #2559

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

Merged
merged 1 commit into from
Aug 21, 2016

Conversation

flovilmart
Copy link
Contributor

Because we call next on each promise resolution, the /me routes would then go into the /:objectId route, this PR makes sure both don't overlap

@codecov-io
Copy link

codecov-io commented Aug 21, 2016

Current coverage is 92.14% (diff: 100%)

Merging #2559 into master will increase coverage by 0.05%

@@             master      #2559   diff @@
==========================================
  Files            97         97          
  Lines         11924      11927     +3   
  Methods        1457       1454     -3   
  Messages          0          0          
  Branches       1926       1929     +3   
==========================================
+ Hits          10981      10990     +9   
+ Misses          943        937     -6   
  Partials          0          0          

Powered by Codecov. Last update 9ab488b...4cc12f9

@drew-gross
Copy link
Contributor

Good catch!

@flovilmart flovilmart merged commit 23e47f2 into master Aug 21, 2016
@drew-gross drew-gross deleted the routing-improvements branch August 22, 2016 03:54
@steven-supersolid
Copy link
Contributor

Are we sure we shouldn't instead avoid calling next() when we send a response? Seems like that is the standard way to handle overlapping routes.

@flovilmart
Copy link
Contributor Author

By not calling next, you prevent middlewares to run, and I will need it in a foreseeable future to cleanup caches or do other manipulations. This was added by @blacha because that helps with profiling time and logging responses which is a valid use case.

bamwang pushed a commit to bamwang/parse-server that referenced this pull request Aug 29, 2016
caoer added a commit to caoer/parse-server that referenced this pull request Aug 29, 2016
* ParsePlatform/master: (100 commits)
  Only allow basic auth credentials with a known appId (parse-community#2574)
  vk.com provider registered (parse-community#2579)
  chore(package): update parse-server-push-adapter to version 1.1.0 (parse-community#2588)
  vk.com auth data manager implemented (parse-community#2578)
  Fix a typo (parse-community#2563)
  Makes sure routes don't overlap and yield a header set error (parse-community#2559)
  Postgres: $all, $and CLP and more (parse-community#2551)
  Changelog 2.2.18 (parse-community#2558)
  chore(package): update winston-daily-rotate-file to version 1.3.0 (parse-community#2547)
  chore(package): update parse-server-s3-adapter to version 1.0.5 (parse-community#2536)
  Adds bcrypt native binding for better login performance (parse-community#2549)
  chore(package): update mongodb to version 2.2.7 (parse-community#2554)
  Make parse-server cloud code logging closer parse.com legacy (parse-community#2550)
  chore(package): update pg-promise to version 5.3.1 (parse-community#2519)
  Postgres: Operations, Hooks, OAuth login, Files support (parse-community#2528)
  Syncing afterSave/afterDelete trigger calls (Issue parse-community#2489) (parse-community#2499)
  Updated README.md (parse-community#2538)
  Fix capitalization, typo, and grammar mistake (parse-community#2533)
  Update ISSUE_TEMPLATE.md
  fix typo (parse-community#2525)
  ...
@flovilmart flovilmart modified the milestone: 2.2.19 Aug 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants