You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, ui-grid's selection doesn't seem to behave well with grouping. When a group header is clicked, it does not select the group header. See below:
Fig 1: Problematic Bug in Grouping Selection
This can be overcome by keeping track of the transactions that are grouped, but it has to be a hack. The previous version of the Journal (outside of refactor-journal-tools) did this in a complicated fashion - see the GridGrouping Service.
The question is: what behavior do we want? I see several possibilities:
Check the header row when any element in the group is selected.
Only check the header row if all elements in the group are selected.
Default behavior (never check the header row).
To get the first two behaviors, we will need to manually track selection in a service. There are some optimizations we can do, but it will be ugly no matter what.
What behavior do we think is the best? Our initial feedback from users suggested they really wanted the header row to be checked at some point.
/cc @IMA-WorldHealth/bhima-core what do you think?
The text was updated successfully, but these errors were encountered:
2085: refactor: Posting Journal and Associated Tools r=mbayopanda a=jniles
This Pull Request finalizes the refactor of the Posting Journal and associated modules. The commit history contains a full list of changes. In brief:
1. Editing has been moved out into a modal. By breaking out the editing code, the complexity of the Posting Journal is reduced. It also enforces editing a single transaction at a time.
2. The Trial Balance has moved into Stored Procedures. This separates the JS code from the SQL code and speeds up the execution of the Trail Balance slightly.
3. The Trial Balance no longer reloads data between `$state` changes. The modal is much more snappy than previous.
4. Links to the receipts/documents/patients associated with each transaction are embedded in the Posting Journal. This makes it easy to find the details associated with a given transaction.
5. The Posting Journal is able to load "posted" transactions. To accommodate this, the Posting Journal footer has been improved to show the number of unposted or posted transactions. Additionally, the "Posted Journal" module has been removed.
There have been a number of miscellaneous bug fixes addressed as well. As with any change, this may introduce new bugs specific to the changes listed above.
Partially addresses #1432.
Closes#1034.
Closes#1163.
Closes#1402.
Closes#1500.
Closes#1640.
Closes#1659.
Closes#1716.
Closes#1717.
Closes#1724.
Closes#1832.
Closes#1839.
Closes#1921.
Closes#1928.
Closes#1934.
Closes#1943.
Closes#1944.
Closes#1948.
Closes#1950.
Closes#1961.
Closes#2031.
Closes#2041.
---
### TODO Before Merge
- [x] Ensure all keys are translated into both French and English
- [x] Ensure tests pass
- [x] Make sure all filters/links work on Posting Journal page.
- [x] Make sure all filters/links work on the Trial Balance
- [x] Ensure all editors work as expected.
- [x] Ensure that new code passes lint checks.
By default,
ui-grid
's selection doesn't seem to behave well with grouping. When a group header is clicked, it does not select the group header. See below:Fig 1: Problematic Bug in Grouping Selection
This can be overcome by keeping track of the transactions that are grouped, but it has to be a hack. The previous version of the Journal (outside of
refactor-journal-tools
) did this in a complicated fashion - see the GridGrouping Service.The question is: what behavior do we want? I see several possibilities:
To get the first two behaviors, we will need to manually track selection in a service. There are some optimizations we can do, but it will be ugly no matter what.
What behavior do we think is the best? Our initial feedback from users suggested they really wanted the header row to be checked at some point.
/cc @IMA-WorldHealth/bhima-core what do you think?
The text was updated successfully, but these errors were encountered: