-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open Next Config validation #646
Comments
I think the main issue here is that we are mixing the My take on this is that we should only use As for the prerequisite that you mentionned an easy fix would be to add an opennextjs-aws/packages/open-next/src/plugins/resolve.ts Lines 57 to 67 in f685dde
We should never rely on the name btw (that's my bad) as it could be a custom override.
That's a good idea, but this will need to be done on a per function basis because each one could use very different overrides. We could compute some kind of OverrideObject that would contain everything we need We can merge #642 and handle all of this in a different PR |
See:
I was looking at improving the configuration validation after the comment in #642
However I think a prerequisite would be to refactor the code before we do the validation:
Maybe we should:
@conico974, you have much more experience than me with the codebase, what do you think?
The text was updated successfully, but these errors were encountered: