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

Add Code of Conduct #3

Closed
arthurkhlghatyan opened this issue Jan 2, 2021 · 0 comments · Fixed by #7
Closed

Add Code of Conduct #3

arthurkhlghatyan opened this issue Jan 2, 2021 · 0 comments · Fixed by #7
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@arthurkhlghatyan
Copy link
Owner

Additional information can be found here.

@arthurkhlghatyan arthurkhlghatyan added documentation Improvements or additions to documentation enhancement New feature or request labels Jan 2, 2021
@arthurkhlghatyan arthurkhlghatyan linked a pull request Jan 2, 2021 that will close this issue
arthurkhlghatyan added a commit that referenced this issue Jan 2, 2021
arthurkhlghatyan added a commit that referenced this issue Jan 5, 2021
* Ensure web assembly support in CI #2

* Add Code of Conduct #3

* Upgrade version of Tokio to 1.0 #5: Need to also upgrade reqwest

* Minor changes
- Configure CI to publish crate version on master branch build #8
- Add missing fields for GraphQLErrorMessage struct #4: Still need to specify path field
- Rollback tokio to v0.2 for now

* Minor changes
- Final struct representation #4
- Upgrade to tokio V1 but still doesn't work #5

* #5 Upgrade to reqwest 0.11 to support tokio v1

* Fix formatting
arthurkhlghatyan added a commit that referenced this issue Jan 5, 2021
* Ensure web assembly support in CI #2

* Add Code of Conduct #3

* Upgrade version of Tokio to 1.0 #5: Need to also upgrade reqwest

* Minor changes
- Configure CI to publish crate version on master branch build #8
- Add missing fields for GraphQLErrorMessage struct #4: Still need to specify path field
- Rollback tokio to v0.2 for now

* Minor changes
- Final struct representation #4
- Upgrade to tokio V1 but still doesn't work #5

* #5 Upgrade to reqwest 0.11 to support tokio v1

* Fix formatting

* Update version number
arthurkhlghatyan added a commit that referenced this issue Jan 5, 2021
* Ensure web assembly support in CI #2

* Add Code of Conduct #3

* Upgrade version of Tokio to 1.0 #5: Need to also upgrade reqwest

* Minor changes
- Configure CI to publish crate version on master branch build #8
- Add missing fields for GraphQLErrorMessage struct #4: Still need to specify path field
- Rollback tokio to v0.2 for now

* Minor changes
- Final struct representation #4
- Upgrade to tokio V1 but still doesn't work #5

* #5 Upgrade to reqwest 0.11 to support tokio v1

* Fix formatting

* Update version number

* Add change log vor V1
arthurkhlghatyan pushed a commit that referenced this issue Mar 10, 2022
* Fix error and Improvements struct (#1)

* Fixed failing compilation with `serde::export`

* Make the "use" part nicer

thanks @ibraheemdev <3

Co-authored-by: Ibraheem Ahmed <ibrah1440@gmail.com>

* Change endpoint types to String, Remove lifetime

Co-authored-by: vyneer <vyneer@protonmail.com>
Co-authored-by: vyneer <41237021+vyneer@users.noreply.github.com>
Co-authored-by: Ibraheem Ahmed <ibrah1440@gmail.com>

* Add timeout when creating client (#2)

* Derive Clone and Debug (#3)

* Fix unwrap (#4)

* Add unwrap api

* Remove unwrap

* Helpful error message

* Use serde_json and helpful error message

* Helpful error (#5)

* Helpful error message

* Use serde_json and helpful error message

* Fix test

* Wasm support (#6)

* Clippy

* Fix wasm build

* Format

Co-authored-by: vyneer <vyneer@protonmail.com>
Co-authored-by: vyneer <41237021+vyneer@users.noreply.github.com>
Co-authored-by: Ibraheem Ahmed <ibrah1440@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant