Currently, we use Native filter on Superset version 1.2, but looks like The actual time range does not show correctly with SIP-15 (in the SIP-15 the time range must is [inclusive, exclusive) ). So that mean the actual time range and the tool tip must show label as: from_date <= col < to_date.

Expected results

![image](https://user-images.githubusercontent.com/37523968/130939207-7ff847a

It seems we have a user-contributed task for SodaSQL that we don't expose in our API documentation, making it very hard to discover; task definition and docstrings here: https://github.com/PrefectHQ/prefect/blob/5de58efaba956b431335d99acab07eaf6a362e1b/src/prefect/tasks/sodasql/sodasql_tasks.py

We should add this to our reference docs using [our development guidelines](https://docs.prefect.io/c

Describe the bug
data docs columns shrink to 1 character width with long query

To Reproduce
Steps to reproduce the behavior:

1. make a batch from a long query string
2. run validation
3. render result to data docs
4. See screenshot
   <img width="1525" alt="Data_documentation_compiled_by_Great_Expectations" src="https://user-images.githubusercontent.com/928247/103230647-30eca500-4

The fs:ReadConfig permission on the resource "*" is required when viewing a specific repository from the UI.

if they are not class methods then the method would be invoked for every test and a session would be created for each of those tests.

`class PySparkTest(unittest.TestCase):
@classmethod
def suppress_py4j_logging(cls):
logger = logging.getLogger('py4j')
logger.setLevel(logging.WARN)

@classmethod
def create_testing_pyspark_session(cls):
    return Sp

Brief Description of Fix

When I see docs I found [get_features_targets page](https://pyjanitor-devs.github.io/pyjanitor/reference/janitor.functions/janitor.get_features_targe

In the repository handler

• removeEntity tries to delete then if delete is not supported issues a purge, the purge method issues an audit log
• There are 2 callers to purgeRelationship only one of which audit logs

This is inconsistent.
I suggest we move the relationship audit log to the purge method, which means that both callers will audit log.

We have a new cookbook section: https://github.com/ploomber/projects/tree/master/cookbook

where we add minimal examples for certain use cases, we should add links to each one on the relevant sections in the docs