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
[10.0][FIX] website patient form delete button #237
[10.0][FIX] website patient form delete button #237
Conversation
Tests are failing from medical_patient_disease. Will leave for now. |
I'm good with the dependency. We can think about breaking it up later if we find a use case. Weird that tests are failing... why is that not the case on release/10.0? Did you base from that? |
Yup from release/10.0. I've noticed it fail on my local build in the past as well. Interesting that it's showing up now. |
* Add to medical_abstract_entity_view_search
* Add access rules for patient diseases
0e11d96
to
098ca88
Compare
Rebased now that #238 is merged |
Codecov Report
@@ Coverage Diff @@
## release/10.0 #237 +/- ##
=============================================
Coverage 85.17% 85.17%
=============================================
Files 123 123
Lines 2293 2293
=============================================
Hits 1953 1953
Misses 340 340 |
woot @lasley thanks for the fix. All checks passing now. |
This pull request addresses the following:
Question
I added medical_patient_disease as a dependency to website_portal_medical_patient. Is that ok? Perhaps we should have a website_portal_medical_patient_disease module or something so that a website module can be directly mapped to the backend disease module.
The issue is associated with adding portal access to medical.patient.disease