-
Notifications
You must be signed in to change notification settings - Fork 9
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(runtime): fixed incorrect parsing of return values #453
Conversation
@@ -3,7 +3,9 @@ import checkSecret from '../game/checkSecret'; | |||
|
|||
export default async function guessSecret(secret: string): Promise<string> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
export default async function guessSecret(secret: string): Promise<string> | |
export default async function guessSecret(secret: number): Promise<string> |
Is this a good idea? It feels more logical to me. The only consequence is that we have to change the requests from GET to POST so we can provide the correct content type.
|
||
import { REQUESTS } from '../_fixtures/services/Remote.fixture'; | ||
|
||
const remote = new Remote('http://localhost:3000'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we create the remote in the fixture?
Fixes #451
Changes proposed in this pull request:
@MaskingTechnology/jitar