-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OP-1363 | Fix NullPointerexception #2089
base: develop
Are you sure you want to change the base?
Conversation
Co-authored-by: David B Malkovsky <[email protected]>
Co-authored-by: David B Malkovsky <[email protected]>
Co-authored-by: David B Malkovsky <[email protected]>
@@ -1197,6 +1197,7 @@ angal.newbill.payment.btn.key | |||
angal.newbill.paymentmadebeforebilldate.msg = Payment made before bill date. | |||
angal.newbill.paymentreceipt.btn = Payment Receipt | |||
angal.newbill.paymentreceipt.btn.key = N | |||
angal.newbill.pleasefindpatientbeforeremotehim.msg = Please find the patient first before trying to remove him. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think "him"/"her" is not very professional here, also I don't think the suggestion make sense (no one wants to find a record in order to suddenly remove it).
Why we don't make just the button doing nothing if patient is null?
Also, we can disable the button when no patient is selected
See OP-1363.