Skip to content

Conversation

@tomq42
Copy link

@tomq42 tomq42 commented Oct 21, 2018

Allow the ability to delay the update of the schema through a config
option. By default this is 0, leaving the behaviour unchanged, and no
penalty is paid.
If the delay is set to a non zero value, it only updates the schema if no
changes to the whiteboard have happened within that delay timeout.

Also fixed up a couple of things with the whiteboard. Using
policy=DYNAMIC is the normal approach, the component can activate
and gets references added as appropriate. The "typesProviders" method
was in error as the name didn't match the unbind. I believe that what
was happenning before is that the component was being activated
and deactivated each time a new reference was added. Now it's activated
once and the whiteboard works correctly.

Note that my preference would be to set the default delay to 150ms.
This will give improved behaviour for most people in my opinion.
I've left the default as 0 though so that the current behaviour is maintained,
and there is no impact of this change at all otherwise.

Allow the ability to delay the update of the schema through a config
option. By default this is 0, leaving the behaviour unchanged, and no
penalty is paid.
If the delay is set to a non zero value, it only updates the schema if no
changes to the whiteboard have happened within that delay timeout.

Also fixed up a couple of things with the whiteboard. Using
policy=DYNAMIC is the normal approach, the component can activate
and gets references added as appropriate. The "typesProviders" method
was in error as the name didn't match the unbind. I believe that what
was happenning before is that the component was being activated
and deactivated each time a new reference was added. Now it's activated
once and the whiteboard works correctly.
@oliemansm oliemansm merged commit bca69e6 into graphql-java-kickstart:master Oct 27, 2018
@oliemansm oliemansm added this to the 6.2.1 milestone Oct 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants