feat: exports stripComments

[cheton]

PR Type

enhancement, tests

---

Description

• Implemented the stripComments function to strip comments from G-code lines, enhancing the parsing capabilities.
• Refactored the comment stripping logic into a new function stripCommentsEx for better modularity.
• Added and exported the stripComments function for external use.
• Added comprehensive tests for the stripComments function to ensure correct parsing of comments in various scenarios.

---

Changes walkthrough 📝

	Relevant files
Tests	index.test.js Add tests for `stripComments` function in G-code parsing  src/tests/index.test.js Added tests for stripComments function. Verified correct parsing of comments in G-code lines. +5/-1
Enhancement	index.js Implement and export `stripComments` function for G-code  src/index.js Implemented stripComments function to remove comments from G-code lines. Refactored comment stripping logic into stripCommentsEx. Exported stripComments for external use. +76/-76

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Potential Overflow The openParens counter uses Math.min/max with Number.MAX_SAFE_INTEGER but could still potentially overflow with deeply nested comments. Consider adding validation for maximum nesting depth. Code Smell The stripCommentsEx function is quite long and handles multiple responsibilities. Consider breaking it down into smaller, more focused functions for better maintainability.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.36%. Comparing base (0df4f3d) to head (141f5bc).

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #10      +/-   ##
==========================================
- Coverage   93.46%   93.36%   -0.10%     
==========================================
  Files           1        1              
  Lines         199      196       -3     
==========================================
- Hits          186      183       -3     
  Misses         13       13              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Detect and handle malformed comments with unclosed parentheses Handle unclosed parentheses in comments by adding a check after the parsing loop to ensure all parentheses are properly closed. src/index.js [91-127] for (let i = 0; i < line.length; i++) { // ... parsing logic ... } +if (openParens > 0) { + throw new Error('Unclosed parentheses in comment'); +} strippedLine = strippedLine.trim(); Suggestion importance[1-10]: 8 Why: This is a critical validation that ensures proper comment syntax, preventing silent failures when parsing malformed G-code. The suggestion adds important error handling for a common syntax error case.	8
	Prevent potential integer overflow and excessive nesting in comment parsing Add error handling for potential integer overflow in nested parentheses counting. While unlikely, deeply nested comments could cause issues. Consider adding a maximum nesting limit. src/index.js [108] -openParens = Math.min(openParens + 1, Number.MAX_SAFE_INTEGER); +const MAX_NESTING = 1000; // Reasonable limit for G-code comments +openParens = Math.min(openParens + 1, MAX_NESTING); +if (openParens === MAX_NESTING) { + throw new Error('Maximum comment nesting depth exceeded'); +} Apply this suggestion Suggestion importance[1-10]: 7 Why: The suggestion addresses a potential edge case in deeply nested comments that could lead to integer overflow. Adding a reasonable nesting limit with error handling improves code robustness and prevents potential parsing issues.	7

💡 Need additional feedback ? start a PR chat