-
Notifications
You must be signed in to change notification settings - Fork 6
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
docs: auth blog post #23
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Reviewer's Guide by SourceryThis pull request adds a new blog post about Kubernetes authentication and authorization, along with the necessary infrastructure to support a blog section in the documentation. The changes include updates to the project's TODO list, modifications to the documentation structure, and the addition of new files for the blog functionality. File-Level Changes
Tips
|
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.
Hey @grampelberg - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟡 General issues: 1 issue found
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟡 Documentation: 1 issue found
Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.
const Blog = () => { | ||
const { asPath } = useRouter() | ||
|
||
let linkClasses = [ |
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.
suggestion: Consider extracting class list
The list of classes is quite long. Consider extracting this into a separate constant or utility function to improve readability and maintainability of the component.
const LINK_CLASSES = [
'border',
'border-zinc-200',
// ... other classes
]
const Blog = () => {
const { asPath } = useRouter()
const linkClasses = LINK_CLASSES
- Move YAML over to viewport. Should viewport be doing syntax highlighting by | ||
default? How do we do a viewport over a set of lines that require history to | ||
do highlighting? | ||
|
||
- There's a bug somewhere in `log_stream`. My k3d cluster restarted and while I | ||
could get all the logs, the stream wouldn't keep running - it'd terminate | ||
immediately. `stern` seemed to be working fine. Recreating the cluster caused | ||
immediately. `stern` seemed to be working fine. Recreating the cluster causedx |
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.
issue (documentation): Fix typo: 'causedx' should be 'caused'
1d993df
to
cdeddf1
Compare
cdeddf1
to
51d6663
Compare
51d6663
to
c68ba15
Compare
c68ba15
to
4e596d7
Compare
Summary by Sourcery
Add a new blog section to the documentation, including a post on simplifying Kubernetes authentication with OpenID Connect. Enhance the Tailwind CSS configuration to center content across the site.
New Features:
Enhancements:
Documentation: