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.

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: Fix wrong link in the README file #3402

Closed
1 task done
having-fun-serverless opened this issue Dec 4, 2024 · 2 comments · Fixed by #3403
Closed
1 task done

Docs: Fix wrong link in the README file #3402

having-fun-serverless opened this issue Dec 4, 2024 · 2 comments · Fixed by #3403
Assignees
Labels
confirmed The scope is clear, ready for implementation documentation Improvements or additions to documentation

Comments

@having-fun-serverless
Copy link
Contributor

What were you searching in the docs?

Link to the parser documentation is wrong.

Is this related to an existing documentation section?

No response

How can we improve?

Fixing the link

Got a suggestion in mind?

As we speak

Acknowledgment

  • I understand the final update might be different from my proposed suggestion, or refused.
@having-fun-serverless having-fun-serverless added documentation Improvements or additions to documentation triage This item has not been triaged by a maintainer, please wait labels Dec 4, 2024
@having-fun-serverless
Copy link
Contributor Author

Submitted a fix - #3403

@am29d am29d added confirmed The scope is clear, ready for implementation and removed triage This item has not been triaged by a maintainer, please wait labels Dec 6, 2024
@am29d am29d moved this from Triage to Working on it in Powertools for AWS Lambda (TypeScript) Dec 6, 2024
@github-project-automation github-project-automation bot moved this from Working on it to Coming soon in Powertools for AWS Lambda (TypeScript) Dec 6, 2024
Copy link
Contributor

github-actions bot commented Dec 6, 2024

⚠️ COMMENT VISIBILITY WARNING ⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
confirmed The scope is clear, ready for implementation documentation Improvements or additions to documentation
Projects
Development

Successfully merging a pull request may close this issue.

2 participants