Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
flipboard.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Welcome to Flipboard on Mastodon. A place for our community of curators and enthusiasts to inform and inspire each other. If you'd like to join please request an invitation via the sign-up page.

Administered by:

Server stats:

1.2K
active users

flipboard.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#graphql

1 post1 participant0 posts today
Public
Tamás

GraphQL tip: Have the subscription types contain all filterable fields on the top-level.

For example, a Todo event that should allow filtering by user, group, severity, and id, should have these as well as the item itself:

```graphql
type TodoEvent {
userId: ID!
groupId: ID!
todoId: ID!
severity: Severity!
todo: Todo
}
```

Originally, it was the only way for filtering in AppSync, but that changed when it [started supporting filters on nested fields](docs.aws.amazon.com/appsync/la). So, why it's still a best practice?

The primary reason is deletion: this structure makes it easy to support sending an event when the item is deleted and all the filters will work.

Then an additional benefit is when there is a filter that is not present in the entity itself. For example, if a Todo item's `userId` can be changed it is useful to notify the original owner. In that case, a `prevUserId` field can be added to the subscription allowing users to subscribe to events when an item is removed from them.

#graphql #tips #appsync

Originally published [on my blog](advancedweb.hu/shorts/graphql-)

docs.aws.amazon.comDefining enhanced subscriptions filters in AWS AppSync - AWS AppSync GraphQLLearn about enhanced subscription filtering in AWS AppSync.
Public
Tadashi Shigeoka

今夜開催予定のFindy Toolsさん主催のオンライイベントに合わせて、テックブログが公開されました🚀

ADRで意思決定し、そのADRを破棄して新しくADRを作成する実例を紹介します - GraphQLクライアントのキャッシュアルゴリズム変更編 - ROUTE06 Tech Blog tech.route06.co.jp/entry/disca

ADRで意思決定し、そのADRを破棄して新しくADRを作成する実例を紹介します - GraphQLクライアントのキャッシュアルゴリズム変更編 - ROUTE06 Tech Blog
ROUTE06 Tech Blog · ADRで意思決定し、そのADRを破棄して新しくADRを作成する実例を紹介します - GraphQLクライアントのキャッシュアルゴリズム変更編 - ROUTE06 Tech BlogROUTE06 でソフトウェアエンジニアをしている @MH4GF です。2025/03/26 に、Findy Tools さん主催の「実例！フロントエンドの技術選定とその後を ADR から振り返る」というイベントで登壇します。 発表タイトルは「チームの性質によって変わる ADR との向き合い方と、生成 AI 時代のこれから」の予定です。サイボウズ株式会社の @sakito さん、ファインディ株式会社の @puku0x さんとパネルディスカッションも行います。オンラインのイベントなので、ぜひお気軽にご参加ください！ findy-tools.connpass.com 発表に先立ち、私が関わったプロ…
#ADR#Frontend#GraphQL
Public
WetHat💦

A beginner-friendly guide to #REST, #SOAP, #GraphQL, and #gRPC:
➡️ Introduces the distinct advantages of each API type and architecture.
➡️Has examples, such as REST’s use in e-commerce, GraphQL in social apps, and gRPC in microservices.
➡️Highlights emerging API trends like decentralized systems and AI-driven capabilities.

freecodecamp.org/news/learn-ap

freeCodeCamp.org · Learn API Fundamentals and Architecture – A Beginner-Friendly GuideHere are some questions for you: How do you log in to apps with your Google, Apple, or Microsoft account? How do online payments with Paystack or PayPal work? How do apps like Facebook and Instagram share information and notifications? The answer is:...
#Programming#APIs#WebDevelopment
Public *
Winnie 🏳️‍🌈

6 years ago, #GitLab decided that they want to switch from REST to #GraphQL (corresponding epic: gitlab.com/groups/gitlab-org/-, initial discussion took place 8 years ago: gitlab.com/gitlab-org/gitlab-f).

They are not done yet and still introduce bugs and performance issues because of that migration (recent example: gitlab.com/gitlab-org/gitlab/-).

I am not saying that GraphQL is bad in general but I have some doubts that this was a good decision.

GitLabGraphQL everywhere (#1366) · Epics · Epics · GitLab.org · GitLabWe want to get to a point where we use our GraphQL API for as much development as possible. This gives us a number of advantages:
ExploreLive feeds
About