In most cases the service fetches requested data from an external server and creates a need object for each
found data-element in the returned data.
These need objects can then be used and referenced as all other need objects, e.g. by filtering them via
needservice supports all options, which are also available for the need/ req (or any other defined need type) directive.
This include also all custom options defined by needs_extra_options.
Beside this, each service can define own options, which may be needed for the service to work correctly.
Please take a look into the related service documentation to find out what is needed.
For services provided by
Sphinx-Needs please take a look into Services.
.. needservice:: <service>
:tags: awesome, nice
Extra content for each new need
The content of needservice is used as content for all created need objects.
A service may deviate from this behavior and define its own usage.
For example by awaiting a json-string with a more complex configuration or by just ignoring the content.
Please take a look into the related service documentation for more information.