Open MetRonnie opened 2 months ago
At present fragments must be given the same name in order to merge, this isn't a problem because we merge them before issuing the request. Presumably these warnings are being raised during the merging process not at request time?
We could potentially avoid the whole merging process by generating the subscription on demand, this solution is outlined here: https://github.com/cylc/cylc-ui/issues/862#issuecomment-1753266211
We get a lot of these warnings from
graphql-tag
in the console:(The link in the warning is dead)
From https://github.com/apollographql/graphql-tag/issues/269:
However we also get this warning for fragments defined only once in the whole app, because at https://github.com/cylc/cylc-ui/blob/88753e233a99c5d1643b210b2cd98c232ba2e6d8/src/services/workflow.service.js#L546-L550
it is re-evaluating the fragment definitions (which have already been cached the first time) each time the query changes because they are included in the query document.