Uh oh!
There was an error while loading. Please reload this page.
feat(server): serverMode 'ws' option - #2082
Conversation
Codecov Report
@@ Coverage Diff @@## master #2082 +/- ##
==========================================
+ Coverage 94.46% 94.47% +<.01%
==========================================
Files 32 32 Lines 1210 1212 +2 Branches 334 335 +1 ==========================================
+ Hits 1143 1145 +2
Misses 65 65 Partials 2 2
Continue to review full report at Codecov.
|
hiroppy
commented
Jul 1, 2019
@Loonride plz rebase |
4c12f80 to
34f3219Compareknagaitsev
commented
Jul 3, 2019
I just added some tests to confirm through mocks that the server interacts with the socket server implementation correctly. I'm not sure if |
hiroppy
commented
Jul 3, 2019
I think it is ok. |
fbb855a to
68c07baComparealexander-akait
commented
Jul 4, 2019
Something wrong with prettier, need fix |
knagaitsev
commented
Jul 4, 2019
Not sure what the problem was exactly, but seems to be fixed |
* feat(server): server mode ws string option * test(server): rearrange bad host test * test(server): added mock server implementation tests * test(server): remove bad host test temporarily * test(server): re added bad host test
* feat(server): server mode ws string option * test(server): rearrange bad host test * test(server): added mock server implementation tests * test(server): remove bad host test temporarily * test(server): re added bad host test
For Bugs and Features; did you add new tests?
Yes
Motivation / Use-Case
Adds the option
serverMode: 'ws'. Please review and merge #2077 before this.I still want to work on
serverMode-option.test.jsfurther such that it tests to see thatServer.jsinteracts with a socket server implementation correctly. Currently, it only checks thatServer.jscalls the constructor of the server implementation. I will work on this later.Breaking Changes
None
Additional Info