Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs/policy-testing: don't advise to "import future.keywords" #5338

Merged
merged 3 commits into from Nov 2, 2022
Merged

docs/policy-testing: don't advise to "import future.keywords" #5338

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b21482a
docs/policy-testing: don't advise to "import future.keywords"
srenatus Nov 2, 2022
f428ad6
Merge branch 'main' into sr/docs/policy-testing-and-future-keywords
srenatus Nov 2, 2022
e314578
Merge branch 'main' into sr/docs/policy-testing-and-future-keywords
srenatus Nov 2, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 2 additions & 6 deletions docs/content/policy-testing.md
View file
Open in desktop
Expand Up @@ -17,12 +17,8 @@ and reduce the amount of time it takes to modify rules as requirements evolve.
{{< info >}}
The examples in this section try to represent the best practices. As such, they
make use of keywords that are meant to become standard keywords at some point in
time, but have been introduced gradually. These _future keywords_ can be enabled
using

```live:eg/import:module:read_only
import future.keywords
```
time, but have been introduced gradually.
[See the docs on _future keywords_](../policy-language/#future-keywords) for more information.
{{< /info >}}

## Getting Started
Expand Down