You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (Jira)" <ji...@apache.org> on 2020/10/12 09:49:00 UTC
[jira] [Resolved] (SLING-9813) Remove scripted SlingDataFetcher
support
[ https://issues.apache.org/jira/browse/SLING-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz resolved SLING-9813.
----------------------------------------
Resolution: Fixed
Removed that support in [commit d22fb273|https://github.com/apache/sling-org-apache-sling-graphql-core/commit/d22fb2739251aab01f5be7dbbec21f4b2a066d6a]
> Remove scripted SlingDataFetcher support
> ----------------------------------------
>
> Key: SLING-9813
> URL: https://issues.apache.org/jira/browse/SLING-9813
> Project: Sling
> Issue Type: Task
> Components: GraphQL
> Affects Versions: GraphQL Core 0.0.6
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Fix For: GraphQL Core 0.0.8
>
>
> Having rediscussed that with a few people I'm not sure if the scripted data fetchers are really useful and worth the burden of supporting them in the GraphQL Core.
> I suppose that module has a very small number of users so far so I'll go ahead and remove that support. It's easy to re-add if someone really needs it and it's also something that people can implement on their own if needed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)