Add support for mutating Javascript vNext
See original GitHub issueWe should add support for mutating JavaScript vNext (6, 7, etc).
This issue tracks the work done on branch stryker-es6-mutator
Todo:
- Rewrite current es5 mutators using babel
- Remove
IdentitifiedNode
- Rename to stryker-javascript-mutator
- Add unit tests for mutators
- Add deprecation warning when using the es5 mutator.
This issue is closely related to #133
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:8 (4 by maintainers)
Top Results From Across the Web
9. Write your first mutation - Apollo GraphQL Docs
Prototype your mutation in Sandbox Explorer. Open your Sandbox Explorer and click on the plus symbol to add a new tab. Next, click...
Read more >3. Adding mutations to your API - GraphQL Nexus
In this chapter you're going to add some write capability to your API. You'll learn about: Writing GraphQL mutations; Exposing GraphQL objects for...
Read more >add support for MutationObserver · Issue #639 - GitHub
The spec seem to indicate a central place where multiple micro tasks are queued and excuted in order. I can find such place...
Read more >Apollo client.mutate for GraphQL mutation update - Hasura
Mutation and update cache. Now let's do the integration part. Open components/Todo/TodoItem.js and add the following code below the other imports:
Read more >Mutations | Vuex
The only way to actually change state in a Vuex store is by committing a mutation. Vuex mutations are very similar to events:...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Not open source sorry, anyway it’s just a create-react-app 👍
@FezVrasta Not in the initial version but we plan on adding it later on. If you look at this line we don’t specify any options object. In the future we could pass an options object with a plugins sections. This however won’t fix everything as the stryker plugin may not know how to mutate the code.
Note that this plugin is merely for mutating the code. If the input was ES2017 code, the output will be ES2017. In order to run ES2017 code in your environment you may have to transpile it to ES5. That will be handled by a plugin like stryker-babel-transpiler which we plan on developing in the future.
Is your code open source? If not, a demo project would help us test the plugins early on 👍