Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Readonly options

See original GitHub issue

We should refactor most (if not all) stryker-api interfaces to be readonly. This has no effect on the resulting JavaScript. Instead, it has the effect that our TypeScript code interacting with our API will not have undesired side effects.

API: Make options like plugins, maxConcurrentTestRunners, etc… required in the StrykerOptions inteface
API: Remove Config class. Update all related interfaces to take a ReadonlyStrykerOptions instead of Config directly
API: Add the default options in a DefaultOptions frozen object (can be exported from stryker-api/core? @simondel, what do you think?)
Stryker: Update stryker package: update the ConfigReader with a set method that sets options on a StrykerOptions config object.
Rest: Update all packages to use StrykerOptions instead of Config.

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:9 (9 by maintainers)

Top GitHub Comments

1reaction

nicojscommented, Sep 29, 2017

@bicep As @simondel already explained, we don’t have a clear description right now. You can take a look at our contribution guide to see how to run stryker locally.

You can start by taking a look at the main runMutationTest method in the Stryker class. If you have any questions: don’t hesitate to ask via gitter, email or the issue at hand. We’re happy to help.

1reaction

nicojscommented, Sep 28, 2017

Hi bicep, awesome to have you onboard the Stryker train. I think in hindsight that this issue might not be that beginner friendly. You might wanna take a look at others with this label. Issue #336 might be the simplest