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

Fix: check server presence correctly in disambiguiation #983

Merged
merged 4 commits into from
Feb 13, 2020

Conversation

XVincentX
Copy link
Contributor

@XVincentX XVincentX commented Feb 13, 2020

Closes #981

ServerMatch is undefined, not null.

@XVincentX XVincentX force-pushed the fix/check-server-correctly branch 2 times, most recently from d32d133 to f99bfa2 Compare February 13, 2020 11:27
Copy link
Contributor

@karol-maciaszek karol-maciaszek left a comment

Choose a reason for hiding this comment

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

Nice catch, interesting that it came out now. Btw. you hijacked that task from me :)

@XVincentX
Copy link
Contributor Author

I know, but you were busy. Just wanted to close this since it's annoying :)

@XVincentX XVincentX merged commit 34460dd into master Feb 13, 2020
@XVincentX XVincentX deleted the fix/check-server-correctly branch February 13, 2020 12:01
XVincentX added a commit that referenced this pull request Feb 13, 2020
* fix: check server presence correctly

* test: add harness

* test: add router test

* docs: changelog line
XVincentX added a commit that referenced this pull request Feb 13, 2020
* fix: check server presence correctly

* test: add harness

* test: add router test

* docs: changelog line
XVincentX added a commit that referenced this pull request Feb 20, 2020
* add io-ts

* add io-ts-types

* rewrite the function to use the new codec

* feat: integrate in the server

* decoder: fix

* test: rewrite

* Fix: check server presence correctly in disambiguiation (#983)

* fix: check server presence correctly

* test: add harness

* test: add router test

* docs: changelog line

* test: add header tests

* feat: use parsePreferHeader

* refactor: make VSCode happy again

* refactor: handle different param names

* refactor: not cool, but it works

* refactor: simplify

* refactor: read configuration only if mock is true

* Update packages/http-server/src/getHttpConfigFromRequest.ts

Co-Authored-By: Karol Maciaszek <[email protected]>

* refactor: it's plural

* docs: tell people to use the prefer header

* docs: update

* docs: changelog line

* test: add harness for dynamic as header

* docs: difference between header and qs

Co-authored-by: Karol Maciaszek <[email protected]>
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.

PRISM returns 422 for routes with same parent route
2 participants