Define DefaultMfeConfig as non nullable
#43
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What I did
This pull request includes a change to the
getMfeConfig.tsfile to improve type safety and clarity in theDefaultMfeConfigtype definition.Improvements to type safety and clarity:
packages/organization-config/src/getMfeConfig.ts: Modified theDefaultMfeConfigtype definition to ensure non-nullability by wrapping theValidConfigForOrganizationsInCommerceLayer['mfe']type in aNonNullableutility type.How to test
Checklist