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

Show timeout status when test run channel doesn't respond in time #195

Merged
merged 1 commit into from Oct 19, 2020

Conversation

kntsoriano
Copy link
Contributor

No description provided.

Copy link
Member

@ErikSchierboom ErikSchierboom left a comment

Choose a reason for hiding this comment

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

Nice!

@SleeplessByte
Copy link
Member

It might start to be interesting to extract all the hardcoded endpoints in the tests only to a single file, so changing the domain or a route is isolated to a single place.

@kntsoriano kntsoriano merged commit 2199137 into editor Oct 19, 2020
@kntsoriano kntsoriano deleted the editor-timeout branch October 19, 2020 09:04
iHiD pushed a commit that referenced this pull request Oct 23, 2020
* Rewrite in-browser editor component

* Use actual endpoints instead of stubbed endpoints

* Timeout when test run channel does not respond in time (#195)

* Pass solution ID in editor test

* Only use isomorphic-fetch in test environment

* Add accept header

* Make textarea an uncontrolled component

* Switch content to a function

* Add TestRunChannel

* Add JSON type checking

* Cancel fetch when sending a new request and unmounting

* Update app/javascript/utils/typecheck.ts

Co-authored-by: Derk-Jan Karrenbeld <derk-jan+github@karrenbeld.info>

* Move isomorphic-fetch to devDependencies

* Downcase headers for compliance

* Rename to onReceive

Co-authored-by: Derk-Jan Karrenbeld <derk-jan+github@karrenbeld.info>
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.

None yet

4 participants