Dynamically change schema about graphiql HOT 8 CLOSED

Yeah, this seems useful, and probably is a bug. If GraphiQL is provided a new schema, that schema should take effect.

from graphiql.

Schema could be constructed by the fetcher if is not provided. Even with the fix if we change the fetcher and provide a null schema, it will not reconstruct a new one (as the construction is triggered in componentDidMount).
Moving the logic from componentDidMount to another method buildSchema? (which could be called also in componentWillReceiveProps) should solve this too :)

from graphiql.

Great point, the fetcher prop could also update. I just added another commit.

from graphiql.

Dynamically change schema - i'm thinking that this means that graphiQl is supposed to detect new changes in the server's schema once it changes . i always find myself needing to refresh graphiQl to detect new things or changes. I do it via the normal f5 browser refresh. how can i have graphiQl detect new changes . is there anything inbuilt, a refresh button maybe? or how should this be setup?

from graphiql.

You'll first need your server to be able to indicate when this has occurred via some subscribe hook. Check out packages like "watchify" to see how this is done in development environments. Then when your client is made aware that the server schema has changed, you'll need to write the code which refetches and produces a new schema instance to provide to . Thanks to this task, the graphiql view will automatically update.

from graphiql.

none of this is built in , ill have to write it all myself right? thanks

from graphiql.

Correct.

from graphiql.

OK thanks, ill attempt this and see how it goes

from graphiql.