Skip to content
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

Accessing invitation's medication request results with Firestore error #176

Closed
1 task done
arkadiuszbachorski opened this issue Nov 4, 2024 · 0 comments · Fixed by #177
Closed
1 task done

Accessing invitation's medication request results with Firestore error #176

arkadiuszbachorski opened this issue Nov 4, 2024 · 0 comments · Fixed by #177
Assignees
Labels
bug Something isn't working

Comments

@arkadiuszbachorski
Copy link
Contributor

Description

Path: /invitations/PATIENT2/medicationRequests/*

Error:
evaluation error at L79:22 for 'list' @ L79, Property user is undefined on object. for 'list' @ L79

It happens on every dev, staging and locally.

Reproduction

  1. Sign in as owner (doesn't happen for admins)
  2. Go to Patients
  3. Click on patient's invitation

Expected behavior

Medication requests should be queryable.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct and Contributing Guidelines
@arkadiuszbachorski arkadiuszbachorski added the bug Something isn't working label Nov 4, 2024
@pauljohanneskraft pauljohanneskraft linked a pull request Nov 4, 2024 that will close this issue
1 task
pauljohanneskraft added a commit that referenced this issue Nov 4, 2024
# Update access control of nested collection of invitations

## ♻️ Current situation & Problem
#176 


## ⚙️ Release Notes 
*Add a bullet point list summary of the feature and possible migration
guides if this is a breaking change so this section can be added to the
release notes.*
*Include code snippets that provide examples of the feature implemented
or links to the documentation if it appends or changes the public
interface.*


## 📚 Documentation
*Please ensure that you properly document any additions in conformance
to [Spezi Documentation
Guide](https://github.com/StanfordSpezi/.github/blob/main/DOCUMENTATIONGUIDE.md).*
*You can use this section to describe your solution, but we encourage
contributors to document your reasoning and changes using in-line
documentation.*


## ✅ Testing
*Please ensure that the PR meets the testing requirements set by CodeCov
and that new functionality is appropriately tested.*
*This section describes important information about the tests and why
some elements might not be testable.*


### Code of Conduct & Contributing Guidelines 

By submitting creating this pull request, you agree to follow our [Code
of
Conduct](https://github.com/StanfordBDHG/.github/blob/main/CODE_OF_CONDUCT.md)
and [Contributing
Guidelines](https://github.com/StanfordBDHG/.github/blob/main/CONTRIBUTING.md):
- [x] I agree to follow the [Code of
Conduct](https://github.com/StanfordBDHG/.github/blob/main/CODE_OF_CONDUCT.md)
and [Contributing
Guidelines](https://github.com/StanfordBDHG/.github/blob/main/CONTRIBUTING.md).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants