Simple React component to view cached data and test result from API
up vote
0
down vote
favorite
This is only the front end side of things which I have at the moment, as the back end is still being worked on. But as this is my first attempt at a react component, I'd like to know if there is anything I can improve on it.
The component has a text area for viewing the current data stored in the cache within our application, another text area for viewing the result when we send that data off to our API and get a transformed version of the data back, as well as two buttons: one for loading the cached data into one of the text areas and one for calling the API with the cached data. This component is used in development/UAT environment for testing purposes.
class DataRevealer extends React.Component {
constructor(props) {
super(props);
this.state = {input: '', result: ''};
this.getCachedDataHandler = this.getCachedDataHandler.bind(this);
this.transformDataHandler = this.transformDataHandler.bind(this);
this.inputDataChanged = this.inputDataChanged.bind(this);
}
getCachedDataHandler() {
let cachedData = DataRevealActions.getCachedData();
this.setState({input: cachedData});
}
transformDataHandler() {
if (this.state.input) {
let transformedData = DataRevealActions.transformData(this.state.input);
this.setState({result: transformedData});
} else {
alert('No data to transform');
}
}
inputDataChanged(event) {
this.setState({input: event.target.value});
}
get getCachedDataButtonText() {
//TODO: localise string
return 'Get Cached Data';
}
get transformDataButtonText() {
//TODO: localise string
return 'Transform Data';
}
render() {
return (
<div className='data-revealer-container'>
<textarea value={ this.state.input }
className='data-revealer-textarea centred-control'
onChange={ this.inputDataChanged }
/>
<div className='action-buttons centred-control'>
<Button onClick={ this.getCachedDataHandler }
className='data-revealer-button centred-control'>
<span>{ this.getCachedDataButtonText }</span>
</Button>
<Button onClick={ this.transformDataHandler }
className='data-revealer-button centred-control' >
<span>{ this.transformDataButtonText }</span>
</Button>
</div>
<textarea value={ this.state.result }
className='data-revealer-textarea centred-control'
/>
</div>
);
}
}
export default DataRevealer;
Couple of things to note:
- The
Button
is one of our custom controls, it acts as a normal button but with pre-implemented styling tweaks. - The
TODO
may not actually be needed, as the strings may not need to be localised.
DataRevealActions
are where the back-end code will go, once that work is done.
javascript react.js user-interface
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
up vote
0
down vote
favorite
This is only the front end side of things which I have at the moment, as the back end is still being worked on. But as this is my first attempt at a react component, I'd like to know if there is anything I can improve on it.
The component has a text area for viewing the current data stored in the cache within our application, another text area for viewing the result when we send that data off to our API and get a transformed version of the data back, as well as two buttons: one for loading the cached data into one of the text areas and one for calling the API with the cached data. This component is used in development/UAT environment for testing purposes.
class DataRevealer extends React.Component {
constructor(props) {
super(props);
this.state = {input: '', result: ''};
this.getCachedDataHandler = this.getCachedDataHandler.bind(this);
this.transformDataHandler = this.transformDataHandler.bind(this);
this.inputDataChanged = this.inputDataChanged.bind(this);
}
getCachedDataHandler() {
let cachedData = DataRevealActions.getCachedData();
this.setState({input: cachedData});
}
transformDataHandler() {
if (this.state.input) {
let transformedData = DataRevealActions.transformData(this.state.input);
this.setState({result: transformedData});
} else {
alert('No data to transform');
}
}
inputDataChanged(event) {
this.setState({input: event.target.value});
}
get getCachedDataButtonText() {
//TODO: localise string
return 'Get Cached Data';
}
get transformDataButtonText() {
//TODO: localise string
return 'Transform Data';
}
render() {
return (
<div className='data-revealer-container'>
<textarea value={ this.state.input }
className='data-revealer-textarea centred-control'
onChange={ this.inputDataChanged }
/>
<div className='action-buttons centred-control'>
<Button onClick={ this.getCachedDataHandler }
className='data-revealer-button centred-control'>
<span>{ this.getCachedDataButtonText }</span>
</Button>
<Button onClick={ this.transformDataHandler }
className='data-revealer-button centred-control' >
<span>{ this.transformDataButtonText }</span>
</Button>
</div>
<textarea value={ this.state.result }
className='data-revealer-textarea centred-control'
/>
</div>
);
}
}
export default DataRevealer;
Couple of things to note:
- The
Button
is one of our custom controls, it acts as a normal button but with pre-implemented styling tweaks. - The
TODO
may not actually be needed, as the strings may not need to be localised.
DataRevealActions
are where the back-end code will go, once that work is done.
javascript react.js user-interface
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
This is only the front end side of things which I have at the moment, as the back end is still being worked on. But as this is my first attempt at a react component, I'd like to know if there is anything I can improve on it.
The component has a text area for viewing the current data stored in the cache within our application, another text area for viewing the result when we send that data off to our API and get a transformed version of the data back, as well as two buttons: one for loading the cached data into one of the text areas and one for calling the API with the cached data. This component is used in development/UAT environment for testing purposes.
class DataRevealer extends React.Component {
constructor(props) {
super(props);
this.state = {input: '', result: ''};
this.getCachedDataHandler = this.getCachedDataHandler.bind(this);
this.transformDataHandler = this.transformDataHandler.bind(this);
this.inputDataChanged = this.inputDataChanged.bind(this);
}
getCachedDataHandler() {
let cachedData = DataRevealActions.getCachedData();
this.setState({input: cachedData});
}
transformDataHandler() {
if (this.state.input) {
let transformedData = DataRevealActions.transformData(this.state.input);
this.setState({result: transformedData});
} else {
alert('No data to transform');
}
}
inputDataChanged(event) {
this.setState({input: event.target.value});
}
get getCachedDataButtonText() {
//TODO: localise string
return 'Get Cached Data';
}
get transformDataButtonText() {
//TODO: localise string
return 'Transform Data';
}
render() {
return (
<div className='data-revealer-container'>
<textarea value={ this.state.input }
className='data-revealer-textarea centred-control'
onChange={ this.inputDataChanged }
/>
<div className='action-buttons centred-control'>
<Button onClick={ this.getCachedDataHandler }
className='data-revealer-button centred-control'>
<span>{ this.getCachedDataButtonText }</span>
</Button>
<Button onClick={ this.transformDataHandler }
className='data-revealer-button centred-control' >
<span>{ this.transformDataButtonText }</span>
</Button>
</div>
<textarea value={ this.state.result }
className='data-revealer-textarea centred-control'
/>
</div>
);
}
}
export default DataRevealer;
Couple of things to note:
- The
Button
is one of our custom controls, it acts as a normal button but with pre-implemented styling tweaks. - The
TODO
may not actually be needed, as the strings may not need to be localised.
DataRevealActions
are where the back-end code will go, once that work is done.
javascript react.js user-interface
This is only the front end side of things which I have at the moment, as the back end is still being worked on. But as this is my first attempt at a react component, I'd like to know if there is anything I can improve on it.
The component has a text area for viewing the current data stored in the cache within our application, another text area for viewing the result when we send that data off to our API and get a transformed version of the data back, as well as two buttons: one for loading the cached data into one of the text areas and one for calling the API with the cached data. This component is used in development/UAT environment for testing purposes.
class DataRevealer extends React.Component {
constructor(props) {
super(props);
this.state = {input: '', result: ''};
this.getCachedDataHandler = this.getCachedDataHandler.bind(this);
this.transformDataHandler = this.transformDataHandler.bind(this);
this.inputDataChanged = this.inputDataChanged.bind(this);
}
getCachedDataHandler() {
let cachedData = DataRevealActions.getCachedData();
this.setState({input: cachedData});
}
transformDataHandler() {
if (this.state.input) {
let transformedData = DataRevealActions.transformData(this.state.input);
this.setState({result: transformedData});
} else {
alert('No data to transform');
}
}
inputDataChanged(event) {
this.setState({input: event.target.value});
}
get getCachedDataButtonText() {
//TODO: localise string
return 'Get Cached Data';
}
get transformDataButtonText() {
//TODO: localise string
return 'Transform Data';
}
render() {
return (
<div className='data-revealer-container'>
<textarea value={ this.state.input }
className='data-revealer-textarea centred-control'
onChange={ this.inputDataChanged }
/>
<div className='action-buttons centred-control'>
<Button onClick={ this.getCachedDataHandler }
className='data-revealer-button centred-control'>
<span>{ this.getCachedDataButtonText }</span>
</Button>
<Button onClick={ this.transformDataHandler }
className='data-revealer-button centred-control' >
<span>{ this.transformDataButtonText }</span>
</Button>
</div>
<textarea value={ this.state.result }
className='data-revealer-textarea centred-control'
/>
</div>
);
}
}
export default DataRevealer;
Couple of things to note:
- The
Button
is one of our custom controls, it acts as a normal button but with pre-implemented styling tweaks. - The
TODO
may not actually be needed, as the strings may not need to be localised.
DataRevealActions
are where the back-end code will go, once that work is done.
javascript react.js user-interface
javascript react.js user-interface
asked Aug 8 at 7:52
Danny Goodall
1259
1259
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
You can just remove the TODO until it's needed. The code will be easier to follow and if someone needs to localize later, they can figure it out themselves. It's clutter.
DataRevealActions
would probably be nice to pass in as properties, so the component is configurable. You could pass it in as now, or just have two different properties,getCachedData
andtransformData
.
Otherwise, looks great!
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You can just remove the TODO until it's needed. The code will be easier to follow and if someone needs to localize later, they can figure it out themselves. It's clutter.
DataRevealActions
would probably be nice to pass in as properties, so the component is configurable. You could pass it in as now, or just have two different properties,getCachedData
andtransformData
.
Otherwise, looks great!
add a comment |
up vote
0
down vote
You can just remove the TODO until it's needed. The code will be easier to follow and if someone needs to localize later, they can figure it out themselves. It's clutter.
DataRevealActions
would probably be nice to pass in as properties, so the component is configurable. You could pass it in as now, or just have two different properties,getCachedData
andtransformData
.
Otherwise, looks great!
add a comment |
up vote
0
down vote
up vote
0
down vote
You can just remove the TODO until it's needed. The code will be easier to follow and if someone needs to localize later, they can figure it out themselves. It's clutter.
DataRevealActions
would probably be nice to pass in as properties, so the component is configurable. You could pass it in as now, or just have two different properties,getCachedData
andtransformData
.
Otherwise, looks great!
You can just remove the TODO until it's needed. The code will be easier to follow and if someone needs to localize later, they can figure it out themselves. It's clutter.
DataRevealActions
would probably be nice to pass in as properties, so the component is configurable. You could pass it in as now, or just have two different properties,getCachedData
andtransformData
.
Otherwise, looks great!
answered Aug 13 at 3:14
ndp
1,08676
1,08676
add a comment |
add a comment |
Thanks for contributing an answer to Code Review Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f201187%2fsimple-react-component-to-view-cached-data-and-test-result-from-api%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown