[sling-whiteboard] branch master updated: mention partial requirements

[bd...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

bdelacretaz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-whiteboard.git


The following commit(s) were added to refs/heads/master by this push:
     new 4a71082  mention partial requirements
4a71082 is described below

commit 4a71082db2b7f9ff65c18dd12483d5584e6ae90d
Author: Bertrand Delacretaz <bd...@apache.org>
AuthorDate: Tue Jul 13 10:45:09 2021 +0200

    mention partial requirements
---
 sling-org-apache-sling-graphql-schema/README.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/sling-org-apache-sling-graphql-schema/README.md b/sling-org-apache-sling-graphql-schema/README.md
index cdf3abf..a1a2ca3 100644
--- a/sling-org-apache-sling-graphql-schema/README.md
+++ b/sling-org-apache-sling-graphql-schema/README.md
@@ -18,6 +18,9 @@ This module also provides a `SchemaAggregatorServlet` that generates schemas by
 mapping request selectors to lists of partial names. The result can be used directly by the Sling GraphQL
 Core module, which makes an internal Sling request to get the schema.
 
+Partials can also depend on others by declaring the required dependencies by name, to make sure the
+aggregated schemas are valid.
+
 With this mechanism, an OSGi bundle can provide both a partial schema and the Sling data fetching and
 processing services that go with it. This allows a GraphQL "API plane" (usually defined by a specific
 instance of the Sling `GraphQLServlet`) to be built out of several OSGi bundles which each focus on a