GraphQL state

Data visualization for GraphQL state

GraphQL stateとは何ですか?

GraphQL stateはUnknownによって開発されたChromeの拡張機能で、その主な機能は「Data visualization for GraphQL state」です。

拡張機能のスクリーンショット

screenshot
screenshot
screenshot
screenshot

GraphQL state拡張機能のCRXファイルをダウンロード

GraphQL state拡張子のファイルをcrx形式でダウンロードし、ブラウザにChrome拡張機能を手動でインストールするか、crxファイルを友達と共有して簡単にChrome拡張機能をインストールします。

拡張機能の使用方法

                        This Chrome extension will add a panel named "GraphQL state" to your devtools. When you use the framework "https://github.com/babyfish-ct/graphql-state", it can help you debug.

In the "GraphQL state" panel, you will see three tab pages: "Simple states", "Graph states" and "Evict Logs".

1. Simple states
The framework supports simple state management similar to "recoil", this tab page can visualize all simple states for you.

2. Graph states
The framework supports graph state management similar to "Apollo Client" and "Relay", its built-in normalized-cache is used to manage all data and relationships. This tab page can visualize this normalized-cache for you.

3. Evict Logs

This is the core value of the framework.

The essence of UI state is that one main mutation causes N extra mutations, the more complex the UI, the larger the N.

The framework allows developer only focus on main mutation, all the extra mutations will be executed automatically.

Compare with Apollo Client and Relay, after mutation, you neither need to update other affected data in the cache, nor need to determine which queries will be affected and need to be refetched.

When the framework is automatically performing extra mutations, it can choose to modify the cache directly, or it may choose to evict affected data from cache (this will cause related queries to be refetched automatically).

Obviously, the first choice is better than the second choice. This tab page lists the history of the second choice made by the framework, and tells the developer the following information.

i. Why did the framework make the second choice?
ii. Is it possible for developers to intervene in optimization and let framework make the first choice?
iii. If so, what should developers do?                    

拡張機能の基本情報

名前 GraphQL state GraphQL state
ID bhpeanmgkcpkpnkpmemoomlfflmaaddo
公式URL https://chromewebstore.google.com/detail/graphql-state/bhpeanmgkcpkpnkpmemoomlfflmaaddo
説明 Data visualization for GraphQL state
ファイルサイズ 1.16 MB
インストール数 154
現在のバージョン 0.3.1
最終更新日 2021-12-16
公開日 2021-12-15
開発者 Unknown
Eメール [email protected]
支払い方法 free
拡張機能のウェブサイト https://github.com/babyfish-ct/graphql-state
対応言語 en
manifest.json
{
    "update_url": "https:\/\/clients2.google.com\/service\/update2\/crx",
    "name": "GraphQL state",
    "description": "Data visualization for GraphQL state",
    "version": "0.3.1",
    "manifest_version": 3,
    "devtools_page": "devtools.html",
    "icons": {
        "16": "images\/16_16.png",
        "32": "images\/32_32.png",
        "48": "images\/48_48.png",
        "128": "images\/128_128.png"
    },
    "content_scripts": [
        {
            "matches": [
                "http:\/\/*\/*",
                "https:\/\/*\/*"
            ],
            "js": [
                "content-script.js"
            ]
        }
    ]
}