automatic import of python-graphene-federation

3 files changed, 128 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..7e70fb1 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/graphene-federation-3.1.3.tar.gz
diff --git a/python-graphene-federation.spec b/python-graphene-federation.spec
new file mode 100644
index 0000000..995bdc7
--- /dev/null
+++ b/python-graphene-federation.spec
@@ -0,0 +1,126 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-graphene-federation
+Version:	3.1.3
+Release:	1
+Summary:	Federation implementation for graphene
+License:	MIT
+URL:		https://github.com/graphql-python/graphene-federation
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/b1/13/ffded4b290bb2e6a04df1cd1f556ea6415632600037c31aabadbdf4741c8/graphene-federation-3.1.3.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-graphene
+Requires:	python3-graphql-core
+Requires:	python3-black
+Requires:	python3-flake8
+Requires:	python3-mypy
+Requires:	python3-pytest
+Requires:	python3-pytest-cov
+Requires:	python3-pytest
+Requires:	python3-pytest-cov
+
+%description
+## Supported Features
+At the moment it supports:
+* `sdl` (`_service` on field): enable to add schema in federation (as is)
+* `@key` decorator (entity support): enable to perform queries across service boundaries (you can have more than one key per type)
+* `@extend`: extend remote types
+* `external()`: mark a field as external
+* `requires()`: mark that field resolver requires other fields to be pre-fetched
+* `provides()`/`@provides`: annotate the expected returned fieldset from a field on a base type that is guaranteed to be selectable by the gateway.
+Each type which is decorated with `@key` or `@extend` is added to the `_Entity` union.
+The [`__resolve_reference` method](https://www.apollographql.com/docs/federation/api/apollo-federation/#__resolvereference) can be defined for each type that is an entity.
+Note that since the notation with double underscores can be problematic in Python for model inheritance this resolver method can also be named `_resolve_reference` (the `__resolve_reference` method will take precedence if both are declared).
+This method is called whenever an entity is requested as part of the fulfilling a query plan.
+If not explicitly defined, the default resolver is used.
+The default resolver just creates instance of type with passed fieldset as kwargs, see [`entity.get_entity_query`](graphene_federation/entity.py) for more details
+* You should define `__resolve_reference`, if you need to extract object before passing it to fields resolvers (example: [FileNode](integration_tests/service_b/src/schema.py))
+* You should not define `__resolve_reference`, if fields resolvers need only data passed in fieldset (example: [FunnyText](integration_tests/service_a/src/schema.py))
+
+%package -n python3-graphene-federation
+Summary:	Federation implementation for graphene
+Provides:	python-graphene-federation
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-graphene-federation
+## Supported Features
+At the moment it supports:
+* `sdl` (`_service` on field): enable to add schema in federation (as is)
+* `@key` decorator (entity support): enable to perform queries across service boundaries (you can have more than one key per type)
+* `@extend`: extend remote types
+* `external()`: mark a field as external
+* `requires()`: mark that field resolver requires other fields to be pre-fetched
+* `provides()`/`@provides`: annotate the expected returned fieldset from a field on a base type that is guaranteed to be selectable by the gateway.
+Each type which is decorated with `@key` or `@extend` is added to the `_Entity` union.
+The [`__resolve_reference` method](https://www.apollographql.com/docs/federation/api/apollo-federation/#__resolvereference) can be defined for each type that is an entity.
+Note that since the notation with double underscores can be problematic in Python for model inheritance this resolver method can also be named `_resolve_reference` (the `__resolve_reference` method will take precedence if both are declared).
+This method is called whenever an entity is requested as part of the fulfilling a query plan.
+If not explicitly defined, the default resolver is used.
+The default resolver just creates instance of type with passed fieldset as kwargs, see [`entity.get_entity_query`](graphene_federation/entity.py) for more details
+* You should define `__resolve_reference`, if you need to extract object before passing it to fields resolvers (example: [FileNode](integration_tests/service_b/src/schema.py))
+* You should not define `__resolve_reference`, if fields resolvers need only data passed in fieldset (example: [FunnyText](integration_tests/service_a/src/schema.py))
+
+%package help
+Summary:	Development documents and examples for graphene-federation
+Provides:	python3-graphene-federation-doc
+%description help
+## Supported Features
+At the moment it supports:
+* `sdl` (`_service` on field): enable to add schema in federation (as is)
+* `@key` decorator (entity support): enable to perform queries across service boundaries (you can have more than one key per type)
+* `@extend`: extend remote types
+* `external()`: mark a field as external
+* `requires()`: mark that field resolver requires other fields to be pre-fetched
+* `provides()`/`@provides`: annotate the expected returned fieldset from a field on a base type that is guaranteed to be selectable by the gateway.
+Each type which is decorated with `@key` or `@extend` is added to the `_Entity` union.
+The [`__resolve_reference` method](https://www.apollographql.com/docs/federation/api/apollo-federation/#__resolvereference) can be defined for each type that is an entity.
+Note that since the notation with double underscores can be problematic in Python for model inheritance this resolver method can also be named `_resolve_reference` (the `__resolve_reference` method will take precedence if both are declared).
+This method is called whenever an entity is requested as part of the fulfilling a query plan.
+If not explicitly defined, the default resolver is used.
+The default resolver just creates instance of type with passed fieldset as kwargs, see [`entity.get_entity_query`](graphene_federation/entity.py) for more details
+* You should define `__resolve_reference`, if you need to extract object before passing it to fields resolvers (example: [FileNode](integration_tests/service_b/src/schema.py))
+* You should not define `__resolve_reference`, if fields resolvers need only data passed in fieldset (example: [FunnyText](integration_tests/service_a/src/schema.py))
+
+%prep
+%autosetup -n graphene-federation-3.1.3
+
+%build
+%py3_build
+
+%install
+%py3_install
+install -d -m755 %{buildroot}/%{_pkgdocdir}
+if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
+if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
+if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
+if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
+pushd %{buildroot}
+if [ -d usr/lib ]; then
+	find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/lib64 ]; then
+	find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/bin ]; then
+	find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/sbin ]; then
+	find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+touch doclist.lst
+if [ -d usr/share/man ]; then
+	find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
+fi
+popd
+mv %{buildroot}/filelist.lst .
+mv %{buildroot}/doclist.lst .
+
+%files -n python3-graphene-federation -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Mon Apr 10 2023 Python_Bot <Python_Bot@openeuler.org> - 3.1.3-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..52c1450
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+d9c6e80753b061ff5db465f0e17c18de  graphene-federation-3.1.3.tar.gz