feat(medusa): spread config to have custom props in config #1896
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.
As i mentioned here: #1837 custom props getting stripped of the config.
Results in problems in seeding with custom logic and custom props in config, cause there is no way to get this custom props into the service loader i.e.
This allows custom props in the config and still preserves the reserved config from medusa.
Question here is should the custom props inside an object called "customConfig" like @srindom suggested in the issue?
currently i dont see the point in changing the config from the real one loaded.