-
Notifications
You must be signed in to change notification settings - Fork 122
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
Hasura/Postgres type support #195
Comments
Hi there, Sure! I'm not sure in which package this would belong. Maybe we can add a Alternatively, you could publish them in your package and we can just add instructions in our docs for importing them. |
My feeling is that your users would get a lot more use out of them, and that it would be valuable to have them under the same umbrella. I don't have any issue continuing to contribute to their upkeep...but I also suspect it'll be a set-and-forget kind of package. I can also imagine that some of the types would be useful beyond Hasura use — things like iso8601 to DateTime kind of deal. |
Sounds good. Let's add a Let me know if you need anything from me. |
Will do. Thanks @smkhalsa. |
Here's what I'm thinking: First, I'm going to enumerate the serializers that we need. Then, I'm going to write a single serializer, and put it up for review. With an example of usage. You're a lot more familiar with this universe than I am, and I'd love to hear your thoughts. We can tweak as necessary, then I'll dive in fully. That sound good to you? |
Sure, sounds good |
Is this PR solving the issue of JSON field not beeing accessible? @shyndman |
Any progress here? |
Hello there,
I'm in the process of writing an adapter library to easily create Ferry clients for connecting to an Nhost.io Hasura backend.
I was thinking that I'd be super useful to have serializers for the Hasura/Postgres types in your library, given its popularity. Something that could easily be included in the user's build.yaml if needed.
Would you consider accepting a contribution?
Related to nhost/nhost-dart#12
The text was updated successfully, but these errors were encountered: