-
Notifications
You must be signed in to change notification settings - Fork 46
docs: fix a couple of minor docs typos/mistakes #460
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.
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
||
```python | ||
import k8spkg.api.core.v1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this package no longer exists
@@ -604,6 +604,12 @@ mixin PersistentVolumeClaimMixin for PVCProtocol: | |||
} | |||
``` | |||
|
|||
> Note: for the `k8s.api.core.v1` import to work, we need to initialize a module and add the `k8s` module as a dependency: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the first time in this doc where external dependencies are used. Perhaps it's worth mentioning how to run this example.
@@ -450,7 +450,7 @@ _priorityCpuMap = { | |||
"3" = 1024 | |||
} | |||
# Using a dict to simplify logic and the default value is 2048 | |||
_cpu = _priorityCpuMap[_priority] or 2048 | |||
_cpu = _priorityCpuMap[str(_priority)] or 2048 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This example would originally always return 2048 regardless of priority
as the dict expects an str
as the key.
Signed-off-by: Tim Rogowski <[email protected]>
1574eb2
to
51103c0
Compare
Good Catch! LGTM. |
1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):
2. What is the scope of this PR (e.g. component or file name):
Docs in
kcl-lang.io\docs\reference\lang\codelab
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):
4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):
5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links: