Add input validation for empty parameters in utility script

[Vedavyasa21]

Actual Behavior

Description:
The function parseContent() in utils/parse.js (or similar helper file) doesn’t check for empty or undefined input before processing. This may cause unexpected errors if someone calls the function without arguments

The function parseContent() in utils/parse.js (or a similar helper file) doesn’t check for empty or undefined input before processing.
This can cause unexpected runtime errors when the function is called without valid content.

Example:
parseContent(); // Throws undefined error

Expected Behavior

Expected Behavior

The function should validate input and throw a clear, descriptive error when content is missing.
Expected output:
Error: Input content cannot be empty.
Suggested Fix:
Add a simple guard clause:
if (!content) {
throw new Error("Input content cannot be empty.");
}

On what browser(s) are you seeing the problem?

No response

Code of Conduct

• By submitting this issue, I agree to follow Codecademy Doc's Code of Conduct.

For Maintainers

• Labels added
• Issue is assigned

[Priyanshjain10]

Hi! I’d like to claim this issue and work on the input validation for parseContent().
I have 4 merged PRs on this repository and am familiar with the contribution process.
Thanks for the opportunity!

[Vedavyasa21]

Yeah continue with it.

[Priyanshjain10]

Thanks for the approval! I've started working on the input validation for parseContent(). I'll submit a PR with the fix soon.

[Priyanshjain10]

Hello! I'm also starting work on this issue to implement input validation for empty parameters in the utility script. I'll add proper guard clauses to check for empty or undefined inputs in the parseContent() function and ensure it throws clear, descriptive errors as specified in the expected behavior.

[mamtawardhani]

Hey @Priyanshjain10 You’re assigned 🎉 In addition to the documents linked in the description, please also look at the Contribution Guide. After creating a PR, the maintainer(s) (with the collaborator label) will add comments/suggestions to address any revisions before approval

[Priyanshjain10]

Thanks @mamtawardhani for the assignment!

I've investigated the repository structure and couldn't locate the utils/parse.js file or the parseContent() function mentioned in the issue description. After reviewing the codebase, it appears this file may not exist yet.

I'll proceed with creating a new utility module utils/parse.js with the parseContent() function that includes proper input validation as specified in the expected behavior. This will serve as a reusable utility function with best practices for error handling.

The implementation will include:

• Guard clause to check for empty or undefined content
• Clear, descriptive error messages
• Proper error throwing mechanism
• JSDoc documentation for clarity

I'll submit the PR shortly following the contribution guidelines.

[mamtawardhani]

Hey @Vedavyasa21, please specify which file you encountered this error in. I see you've mentioned an error; it would be helpful to locate the file.

@Priyanshjain10, that is not how we do submissions at Codecademy. We first need to figure out the correct path. I'll be closing the PR that you've raised for now due to:

• no correct path
• does not follow Codecademy Standards

[hhsanabri]

Hello @mamtawardhani,
I am trying to complete the 'Contributing to the Codecademy Docs Repository' project and wanted to know if this issue is available so I can contribute?