2017-11-05 16:37:06 -06:00
|
|
|
|
# React
|
|
|
|
|
|
|
|
|
|
|
|
Implement a basic reactive system.
|
|
|
|
|
|
|
|
|
|
|
|
Reactive programming is a programming paradigm that focuses on how values
|
|
|
|
|
|
are computed in terms of each other to allow a change to one value to
|
|
|
|
|
|
automatically propagate to other values, like in a spreadsheet.
|
|
|
|
|
|
|
|
|
|
|
|
Implement a basic reactive system with cells with settable values ("input"
|
|
|
|
|
|
cells) and cells with values computed in terms of other cells ("compute"
|
|
|
|
|
|
cells). Implement updates so that when an input value is changed, values
|
|
|
|
|
|
propagate to reach a new stable system state.
|
|
|
|
|
|
|
|
|
|
|
|
In addition, compute cells should allow for registering change notification
|
|
|
|
|
|
callbacks. Call a cell’s callbacks when the cell’s value in a new stable
|
|
|
|
|
|
state has changed from the previous stable state.
|
|
|
|
|
|
|
2017-12-12 18:11:43 +00:00
|
|
|
|
## Exception messages
|
|
|
|
|
|
|
|
|
|
|
|
Sometimes it is necessary to raise an exception. When you do this, you should include a meaningful error message to
|
|
|
|
|
|
indicate what the source of the error is. This makes your code more readable and helps significantly with debugging. Not
|
|
|
|
|
|
every exercise will require you to raise an exception, but for those that do, the tests will only pass if you include
|
|
|
|
|
|
a message.
|
|
|
|
|
|
|
|
|
|
|
|
To raise a message with an exception, just write it as an argument to the exception type. For example, instead of
|
2018-03-06 00:45:39 +08:00
|
|
|
|
`raise Exception`, you should write:
|
2017-12-12 18:11:43 +00:00
|
|
|
|
|
|
|
|
|
|
```python
|
|
|
|
|
|
raise Exception("Meaningful message indicating the source of the error")
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2018-02-26 12:03:28 -06:00
|
|
|
|
## Running the tests
|
|
|
|
|
|
|
|
|
|
|
|
To run the tests, run the appropriate command below ([why they are different](https://github.com/pytest-dev/pytest/issues/1629#issue-161422224)):
|
|
|
|
|
|
|
|
|
|
|
|
- Python 2.7: `py.test react_test.py`
|
2018-05-26 02:01:55 -07:00
|
|
|
|
- Python 3.4+: `pytest react_test.py`
|
2018-02-26 12:03:28 -06:00
|
|
|
|
|
|
|
|
|
|
Alternatively, you can tell Python to run the pytest module (allowing the same command to be used regardless of Python version):
|
|
|
|
|
|
`python -m pytest react_test.py`
|
|
|
|
|
|
|
2018-03-06 00:45:39 +08:00
|
|
|
|
### Common `pytest` options
|
|
|
|
|
|
|
|
|
|
|
|
- `-v` : enable verbose output
|
|
|
|
|
|
- `-x` : stop running tests on first failure
|
|
|
|
|
|
- `--ff` : run failures from previous test before running other test cases
|
2018-02-26 12:03:28 -06:00
|
|
|
|
|
|
|
|
|
|
For other options, see `python -m pytest -h`
|
|
|
|
|
|
|
2017-11-05 16:37:06 -06:00
|
|
|
|
## Submitting Exercises
|
|
|
|
|
|
|
2018-02-04 11:56:00 -07:00
|
|
|
|
Note that, when trying to submit an exercise, make sure the solution is in the `$EXERCISM_WORKSPACE/python/react` directory.
|
2017-11-05 16:37:06 -06:00
|
|
|
|
|
2018-02-04 11:56:00 -07:00
|
|
|
|
You can find your Exercism workspace by running `exercism debug` and looking for the line that starts with `Workspace`.
|
2017-11-05 16:37:06 -06:00
|
|
|
|
|
|
|
|
|
|
For more detailed information about running tests, code style and linting,
|
|
|
|
|
|
please see the [help page](http://exercism.io/languages/python).
|
|
|
|
|
|
|
|
|
|
|
|
## Submitting Incomplete Solutions
|
2018-03-06 00:45:39 +08:00
|
|
|
|
|
2017-11-05 16:37:06 -06:00
|
|
|
|
It's possible to submit an incomplete solution so you can see how others have completed the exercise.
|