Created by: ens-bwalts
Requirements
- Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion;
- Review the development guidelines for eHive; remember in particular:
- Do not modify code without testing for regression.
- Provide simple unit tests to test the changes.
- If you change the database schema, please follow the instructions for schema changes in the developer guidelines.
- If you change the schema, meadow, or guest language interfaces, please follow the scheme for internal versioning in the developer guidelines.
- The PR must not fail unit testing.
Use case
@mkszuba noted that we have an opportunity to make some readability fixes with the changes brought in with #108. We should make these fixes in 2.5 as well, as long as we're making them - we get a slightly cleaner commit history this way, too.
Description
Added whitespace where it will add clarity, in lines that were new or being changed anyway.
Possible Drawbacks
Authorship of functional change is one commit off on a couple of lines
Testing
Have you added/modified unit tests to test the changes? N/A If so, do the tests pass/fail? N/A Have you run the entire test suite and no regression was detected? Yes