🧪 Add test file for internal/world/parser_factory.go

[theRebelliousNerd]

🎯 What: Missing test file entirely for internal/world/parser_factory.go. The behavior is easily testable.
📊 Coverage: Added tests for NewParserFactory, Register, GetParser, HasParser, Parse, ParseWithFacts, EmitAllFacts, SupportedExtensions, RegisteredLanguages, ProjectRoot, RelativePath, normalizeExtension, and DefaultParserFactory. Included failure scenarios when parser is absent or emits an error, and used a clean mock implementation for deterministic validation.
✨ Result: internal/world/parser_factory.go is now comprehensively covered, addressing the testing gap securely.

---

PR created automatically by Jules for task 14080855643664714533 started by @theRebelliousNerd

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Review limit reached

@theRebelliousNerd, we couldn't start this review because you've used your available PR reviews for now.

Your plan includes 1 review of capacity. Refill in 49 minutes and 15 seconds.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more review capacity refills, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: bad71c63-0a84-43ce-95e0-8dcf3f5b9dab

📥 Commits

Reviewing files that changed from the base of the PR and between 664e51f and f9b0090.

📒 Files selected for processing (3)

• cmd/nerd/chat/.nerd/session.json
• internal/campaign/.nerd/campaigns/c_test_triage/assault/triage/latest.json
• internal/world/parser_factory_test.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jules-14080855643664714533-48a8e359

---

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

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