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

Unable to use client attr because it is used by our client #59

Open
ruscoder opened this issue Mar 23, 2020 · 3 comments
Open

Unable to use client attr because it is used by our client #59

ruscoder opened this issue Mar 23, 2020 · 3 comments
Labels
bug Something isn't working

Comments

@ruscoder
Copy link
Member

Let's remove self.client to self._client

@ruscoder
Copy link
Member Author

ruscoder commented Aug 2, 2023

I'm thinking about _client extenstion in FHIR Resources, so, maybe to choose another name

@ruscoder ruscoder added the bug Something isn't working label Aug 19, 2023
@ruscoder
Copy link
Member Author

ruscoder commented Aug 3, 2024

Renamed to __client__ in 2.0.0

@ruscoder ruscoder closed this as completed Aug 3, 2024
@ruscoder ruscoder reopened this Nov 4, 2024
@ruscoder
Copy link
Member Author

ruscoder commented Nov 4, 2024

sessions = (
            await fhir_client.resources("Session")
            .search(Raw(**{"user:User.id": user.id}))
            .fetch_all()
        )

raises

TypeError: BaseResource.__init__() got multiple values for argument 'client'

because the first argument of BaseResource is still named client.
It needs to be renamed as well.

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

No branches or pull requests

1 participant