With docker, if you set the env variable DEBUG=1 or force the container to start with the -d parameter the logs are not so verbose.

Is there another variable/option to use or is it really an issue?

In section 3.4 (Feature Dependencies), you'll find tables describing the features and their dependencies in terms of user consent and feature policy.

In particular, there's the information in the screen capture I have included here:

The table says that local requires consent for

Not working for django=2.1.3 & djangorestframework==3.9.0

You need to change this:

• URLPattern and URLResolver on line:3, [line:26](https://github.com/manosim/django-rest-framework-docs/blob/94571d05617d24816ba8fdc5e836d17645a88319/rest_framework

Motivation

Being readme-embedded, the documentation is starting to get cluttered and incomprehensible. Interactive playgrounds and use-cases should be provided for each hook and their configurable parameters.

Details

For example, Chakra UI provides concise and comprehensible docs for their components, packed with editable examples usable out of the bo

We're currently at ~96% test coverage. It might be worth investigating what parts of the codebase those remaining 4% correspond to, and try adding/tweaking our tests in order to get us to 100%. Then we can start enforcing full coverage on CI.

Any PR that gets us a little bit closer to that goal very much welcome!

- [ x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

The readme below refers to AddAzureADBearer (a v1 endpoint I believe) when it needs to refer to the updated 2.0 endpoint services.AddProtectedWebApi()...

In #33 we created an ExpandFrom attribute. We now need to go back and add some documentation and usage examples.

You'll definitely want to read #33 and become familiar with the implementation.

Possible Implementation

1. Adding a tutorial for ExpandFrom to docs
   1a. Add a reference to the Documentation list and the table of contents
2. Add a relevant example usage to the NetCoreExampl

Problem: Often, the documentation of the function misses or has a too general description of @value.

Example:
?rsnps::annotations just mentions Value: data.frame of results (independent of the four output options).

Goal: have the structure of the returned data.frame described.