Add solution for Challenge 6 by alimkinpark

[alimkinpark]

Challenge 6 Solution

Submitted by: @alimkinpark
Challenge: Challenge 6

Description

This PR contains my solution for Challenge 6.

Changes

• Added solution file to challenge-6/submissions/alimkinpark/solution-template.go

Testing

• Solution passes all test cases
• Code follows Go best practices

Thank you for reviewing my submission! 🚀

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f63d0328-d140-4f90-bce7-e3a6e44aef18

📥 Commits

Reviewing files that changed from the base of the PR and between bf844ae and 8b79db1.

📒 Files selected for processing (1)

• challenge-6/submissions/alimkinpark/solution-template.go

---

Walkthrough

A new Go solution file is added to the challenge 6 submission directory, implementing the CountWordFrequency function that normalizes text by removing apostrophes, tokenizes into words, converts to lowercase, and returns a frequency map.

Changes

Cohort / File(s)	Summary
Challenge 6 Solution challenge-6/submissions/alimkinpark/solution-template.go	New file implementing CountWordFrequency(text string) map[string]int that tokenizes input on non-alphanumeric boundaries, lowercases tokens, strips apostrophes, and counts word occurrences.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• #609: Implements CountWordFrequency in the challenge6 package with identical function signature and similar word normalization logic.
• #866: Adds the same CountWordFrequency function with apostrophe removal, lowercase conversion, and alphanumeric tokenization.
• #695: Implements CountWordFrequency in challenge6 with matching tokenization and frequency counting behavior.

Poem

🐰 A word-counting quest, so delightfully neat,
Letters and digits in frequency beat!
Apostrophes tumble, case lowered with care,
A frequency map blooms, beyond compare! 📊

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change—adding a solution for Challenge 6 by a specific contributor.
Description check	✅ Passed	The description is directly related to the changeset, explaining the Challenge 6 solution submission with relevant context.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.11.4)

level=error msg="[linters_context] typechecking error: pattern ./...: directory prefix . does not contain main module or its selected dependencies"

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

⚠️ Auto-merge failed

Could not automatically merge this PR: Resource not accessible by integration

A maintainer will need to merge manually.

[github-actions]

⚠️ Auto-merge failed

Could not automatically merge this PR: Resource not accessible by integration

A maintainer will need to merge manually.

[github-actions]

⚠️ Auto-merge failed

Could not automatically merge this PR: Resource not accessible by integration

A maintainer will need to merge manually.

[github-actions]

👋 Action needed for auto-merge

This PR cannot be auto-merged because "Allow edits from maintainers" is enabled. This is a GitHub limitation with automated workflows.

To fix: Please uncheck "Allow edits from maintainers" in the PR sidebar (under the reviewers section), and the PR will be auto-merged in the next cycle.

Alternatively, a maintainer can merge this manually.