Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #2143 +/- ##
==========================================
- Coverage 45.93% 45.89% -0.05%
==========================================
Files 1036 1035 -1
Lines 17150 17167 +17
Branches 3115 3124 +9
==========================================
Hits 7878 7878
- Misses 9272 9289 +17 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
e540f27 to
edb626f
Compare
4a30d27 to
ae6c287
Compare
88cc4f4 to
49ed030
Compare
bc70145 to
beca3c1
Compare
…ownModel as submodels to extend it instead
beca3c1 to
319bb4d
Compare
| * | ||
| * @return {string} | ||
| */ | ||
| set normalized(value) { |
There was a problem hiding this comment.
What happens if value is null or undefined? Could value ever be null or undefined? Maybe not in UI but maybe if passed in URL? What do you think? Goes for all the setters.
There was a problem hiding this comment.
Since queryRouter omits any values that are undefined when computing its params field, the normalized values derived from params will always be usable.
As a result, if a value is passed via URL (which is why the setters exist), neither value nor its equivalent can end up being undefined.
There was a problem hiding this comment.
To clarify, while undefined can't really reach the setters, empty strings can
…tions received in the normalized setter
…l and NumericalComparisonModel
f314b72 to
1443e47
Compare
graduta
left a comment
There was a problem hiding this comment.
Nice effort, seems to be in the right direction. I wanted to ask if you had the opportunity to look at tests or update them? More specifically, given the refactor, what was your testing strategy to ensure consistency across changes?
| * Accounts for the options being either RemoteData or an array. | ||
| * | ||
| * @return {SelectionDropdownModel} the dropdown model | ||
| * @param {object} |
The refactors were all in models that already had tests that checked the effectiveness. However, according to the the back-end code. And the test that checks the effectiveness of the runTypes filter on the front-end, this change did not make a difference. So, I'm not quite sure which tests would be updated. |
…s-to-all-classes-that-extend-FilterModel-and-SelectionModel
I have a JIRA ticket
Notable changes for users:
Notable changes for developers:
Changes made to the database: