iop
/
superset
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Correcting some typos (#19338) 

Co-authored-by: Andreas Burner <andreas.burner@smartstream-stp.com>
This commit is contained in:
ND 2022-03-23 22:19:32 +01:00 committed by GitHub
parent 0ad692511e
commit 7ba06ee944
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/docs/contributing/hooks-and-linting.mdx
View File

@ -39,7 +39,7 @@ We use [Pylint](https://pylint.org/) for linting which can be invoked via:
tox -e pylint tox -e pylint
``` ```
In terms of best practices please advoid blanket disablement of Pylint messages globally (via `.pylintrc`) or top-level within the file header, albeit there being a few exceptions. Disablement should occur inline as it prevents masking issues and provides context as to why said message is disabled. In terms of best practices please avoid blanket disablement of Pylint messages globally (via `.pylintrc`) or top-level within the file header, albeit there being a few exceptions. Disablement should occur inline as it prevents masking issues and provides context as to why said message is disabled.
Additionally, the Python code is auto-formatted using [Black](https://github.com/python/black) which Additionally, the Python code is auto-formatted using [Black](https://github.com/python/black) which
is configured as a pre-commit hook. There are also numerous [editor integrations](https://black.readthedocs.io/en/stable/integrations/editors.html) is configured as a pre-commit hook. There are also numerous [editor integrations](https://black.readthedocs.io/en/stable/integrations/editors.html)

2
docs/docs/installation/configuring-superset.mdx
View File

@ -10,7 +10,7 @@ version: 1
### Configuration ### Configuration
To configure your application, you need to create a file `superset_config.py` and add it to your To configure your application, you need to create a file `superset_config.py` and add it to your
`PYTHONPATH`. If your applcation was installed using docker-compose an alternative configuration is required. See [https://github.com/apache/superset/tree/master/docker#readme](https://github.com/apache/superset/tree/master/docker#readme) for details. `PYTHONPATH`. If your application was installed using docker-compose an alternative configuration is required. See [https://github.com/apache/superset/tree/master/docker#readme](https://github.com/apache/superset/tree/master/docker#readme) for details.
Here are some of the parameters you can set in that file: Here are some of the parameters you can set in that file:
``` ```

6
docs/docs/installation/sql-templating.mdx
View File

@ -120,7 +120,7 @@ In this section, we'll walkthrough the pre-defined Jinja macros in Superset.
The `{{ current_username() }}` macro returns the username of the currently logged in user. The `{{ current_username() }}` macro returns the username of the currently logged in user.
If you have caching enabled in your Superset configuration, then by default the the `username` value will be used If you have caching enabled in your Superset configuration, then by default the the `username` value will be used
by Superset when calculating the cache key. A cache key is a unique identifer that determines if there's a by Superset when calculating the cache key. A cache key is a unique identifier that determines if there's a
cache hit in the future and Superset can retrieve cached data. cache hit in the future and Superset can retrieve cached data.
You can disable the inclusion of the `username` value in the calculation of the You can disable the inclusion of the `username` value in the calculation of the
@ -134,8 +134,8 @@ cache key by adding the following parameter to your Jinja code:
The `{{ current_user_id() }}` macro returns the user_id of the currently logged in user. The `{{ current_user_id() }}` macro returns the user_id of the currently logged in user.
If you have caching enabled in your Superset configuration, then by defaul the the `user_id` value will be used If you have caching enabled in your Superset configuration, then by default the the `user_id` value will be used
by Superset when calculating the cache key. A cache key is a unique identifer that determines if there's a by Superset when calculating the cache key. A cache key is a unique identifier that determines if there's a
cache hit in the future and Superset can retrieve cached data. cache hit in the future and Superset can retrieve cached data.
You can disable the inclusion of the `user_id` value in the calculation of the You can disable the inclusion of the `user_id` value in the calculation of the