Below code does not contains this.setState
import React, { Component } from 'react';
import { render } from 'react-dom';
import ReactChopper from 'react-chopper';
class App extends Component {
constructor(props) {
super(props);
this.state = {
name: 'React'
};
this.modal = ReactChopper(this.state, this);
}
render() {
return (
<div>
<input
name={this.modal.name}
onChange={e => this.modal.name = e.target.value} />
<p>
Bang Bang {this.modal.name}
</p>
</div>
);
}
}
render(<App />, document.getElementById('root'));
//Note : after using this.modal you should not use this.state
Not to develop insecurity by making it higherorder component and wrapping whole react component like other libraries.
Make every develop know whats under the hood its Javascript Proxies.
It will be doing one task only , is to watch any changes on target object and do setState underthehood.
This lib won't be doing multiple task like other react libs do Eg : redux-form , react-form , react-validation ect .. developers pickup these libs for validation and land up doing state management , which is filled up with its limitations and ultimately creating spagetti code.
- Write initial testcases
- Integrate with
circleci
- Add coveralls support
- A Simple demo sandbox app made from
react-chopper
- A Complex computation demo sandbox app made from
react-chopper
- A Super complex computation demo sandbox app made from
react-chopper
- Documentation about
- Testcase that uses
react-chopper
lib from npm - Write some more Complex testcase scenarios for testing
- Use
rollupjs
instead ofwebpack
- Create seperate
develop
for all developer experiments - Setup mechanism to push tested code to
master branch
- Deploy package on npm from
circleci
frommaster branch
- Add debug mode for debuging , watch changes purpose