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

Introduce a abstraction for scalar values #251

Merged
merged 20 commits into from
Oct 23, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -6,4 +6,6 @@ members = [
"juniper_hyper",
"juniper_iron",
"juniper_rocket",
"juniper_warp",
"juniper_warp/examples/warp_server/",
]
13 changes: 13 additions & 0 deletions changelog/master.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,16 @@
# [master] yyyy-mm-dd

## Changes

- Juniper is now generic about the exact representation of scalar values. This
allows downstream crates to add support for own scalar value representations.

There are two use cases for this feature:
* You want to support new scalar types not representable by the provided default
scalar value representation like for example `i64`
* You want to support a type from a third party crate that is not supported by juniper

**Note:** This may need some changes in down stream code, especially if working with
generic code. To retain the current behaviour use `DefaultScalarValue` as scalar value type

[#251](https://github.com/graphql-rust/juniper/pull/251)
2 changes: 1 addition & 1 deletion juniper/Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ expose-test-schema = []
default = [
"chrono",
"url",
"uuid"
"uuid",
]

[dependencies]
Expand Down
Loading