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

Consider making Value::array and Value::structure public #22

Open
vezult opened this issue Oct 7, 2024 · 1 comment
Open

Consider making Value::array and Value::structure public #22

vezult opened this issue Oct 7, 2024 · 1 comment

Comments

@vezult
Copy link

vezult commented Oct 7, 2024

I'm writing a client for a service that is returning complex data. dxr can handle the response...but then I can't really do much with it. I am not using reqwest.

Perhaps there is a better way to do what I am doing...but given my current approach, not being able to use Value::array or Value::structure feels very limiting.

@decathorpe
Copy link
Member

Hm, I'm not sure I understand why you'd need to have these functions public? They're used for constructing values, not for de-structuring them, after all.

Does converting the values into the desired collections with TryFromValue trait implementations not work for your use case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants