Skip to content

change that introduces fix to issue 107#130

Open
jjijon7000 wants to merge 1 commit into
devfrom
fix/issue-107-enum-fields-missing
Open

change that introduces fix to issue 107#130
jjijon7000 wants to merge 1 commit into
devfrom
fix/issue-107-enum-fields-missing

Conversation

@jjijon7000

Copy link
Copy Markdown

Summary

Fix enum fields disappearing from generated blank code.json templates.

This addresses Issue #107, where enum-backed fields were being omitted from the blank code.json even though they are part of the CMS schema. The generator now preserves blank placeholder values for those enum fields instead of letting them get dropped during JSON serialization or overwritten as undefined during metadata merging.

The generated code.json now includes the full schema shape, including:

  • status
  • repositoryHost
  • repositoryVisibility
  • softwareType
  • maintenance
  • repositoryType
  • fismaLevel

A regression test was added to verify the generated PR payload still contains those enum keys in the blank template.

Testing

  • npx jest --runInBand src/__tests__/unit/main.test.ts
  • npx jest --runInBand

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant