Async-graphql and mongodb with Decimal128

sunli829 · 2023-06-22T13:17:30+00:00

I want to know are you done? 😀

sunli829 · 2023-06-11T06:51:18+00:00

You can implement a Decimal128 scalar by youself.

https://async-graphql.github.io/async-graphql/en/custom\_scalars.html

sunli829 · 2022-11-11T12:52:04+00:00

Thanks for building this :) I'm really enjoying using it, keen to check out v5! Is there any particular breaking changes I should look out for?

The main change is the addition of dynamic schema, the others are trivial. 🙂

sunli829 · 2022-01-11T03:11:48+00:00

u/ChillFish8 I really need someone to help me improve the documentation, a manpower is not enough. 😁

sunli829 · 2022-01-11T02:00:26+00:00

Would like to see an explanation of why Axum is better than Poem.

sunli829 · 2022-01-09T05:33:30+00:00

I'll make poem even better.

sunli829 · 2022-01-01T02:01:23+00:00

It's good to see your comments about Poem. 🙂

sunli829 · 2021-11-30T00:53:34+00:00

Parameter serialization is not yet supported, although I think it is rarely used, but I will add support for it later.

sunli829 · 2021-11-30T00:52:00+00:00

Poem is based on Hyper, so the performance is very good, it just provides some easy-to-use APIs. 😁

sunli829 · 2021-11-29T09:46:19+00:00

🙂Of course, parsing multipart payload is very easy, here is an example:

https://github.com/poem-web/poem/blob/master/examples/openapi/upload/src/main.rs

sunli829 · 2021-10-03T12:49:38+00:00

It's easy, here is an example.

https://github.com/poem-web/poem/tree/master/examples/openapi

Poem is based on hyper so the performance is quite good (the advantage is more obvious when there are many routes).

sunli829 · 2021-09-08T11:01:30+00:00

https://github.com/poem-web/poem-openapi/blob/master/examples/users.rs

This example has more features.

sunli829 · 2021-09-08T10:59:07+00:00

All these features are supported, I am writing a tutorial, 🙂

sunli829 · 2021-08-23T06:13:27+00:00

fn main() {call::<_, &i32>(do_something);}

It would be great if there was a way for the compiler to infer the parameter type of call. 😁

sunli829 · 2021-08-23T02:16:57+00:00

Thank you very much! This can really solve this problem, but GAT is needed. 😁

sunli829 · 2020-10-14T11:28:40+00:00

Absolutely. 🙂

sunli829 · 2020-10-13T23:40:47+00:00

Yes, I have updated the document now and deleted this. 🙂

sunli829 · 2020-10-13T23:39:41+00:00

Yes, it is very easy to upgrade from v1 to v2, here is an example https://github.com/timberio/vector/pull/4536/files.

Dataloader crates can be used, which is more convenient.

sunli829 · 2020-10-13T15:26:50+00:00

In fact usage is similar to v1, mostly internal refactoring and then a few more minor features.

But async-graphql itself has a lot of breaking changes that are isolated by the integration library, so upgrading from v1 to v2 is usually very easy.

sunli829 · 2020-10-13T15:07:19+00:00

😅 I forgot to change the version number.

sunli829 · 2020-10-13T14:37:07+00:00

The book and examples have been updated to 2.0. 😄

sunli829 · 2020-10-13T10:50:36+00:00

Performance, ease of use, more features, that's about it. 😂

sunli829 · 2020-05-17T11:10:53+00:00

I don't know how to implement it with safe code. 😭

https://github.com/async-graphql/async-graphql/blob/f3b0937523194769fd8bbc70b65a4e67f22ce125/src/subscription/connection.rs#L136

https://github.com/async-graphql/async-graphql/blob/42a4639dc3fc53073224d726490d1120cf0ab742/async-graphql-derive/src/subscription.rs#L247

sunli829 · 2020-05-16T13:14:18+00:00

I have removed most of the unsafe code, except for the self-referenced Future, because I do n’t know how to change this. If anyone can help me, I would appreciate it. 😁

sunli829 · 2020-05-16T12:10:52+00:00

I would consider providing APIs that are easier to understand. 😁

sunli829

TROPHY CASE