You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
Truffle should error when it receives a config field that is unrecognized. Doing this helps users to spot typographical errors in field names.
Unfortunately this change may make things more challenging for plugin developers who want users to be able to specify additional fields in the config object for their plugin to use. If this is the case, then as part of this change it should be possible for plugins to specify their config requirements so that Truffle can check it accordingly.
Note: This was captured from an internal session where we discussed potential future breaking changes for major releases. Until the team assigns this ticket, this is merely a proposal, and not a commitment to make this specific change.
The text was updated successfully, but these errors were encountered:
Truffle should error when it receives a config field that is unrecognized. Doing this helps users to spot typographical errors in field names.
Unfortunately this change may make things more challenging for plugin developers who want users to be able to specify additional fields in the config object for their plugin to use. If this is the case, then as part of this change it should be possible for plugins to specify their config requirements so that Truffle can check it accordingly.
Note: This was captured from an internal session where we discussed potential future breaking changes for major releases. Until the team assigns this ticket, this is merely a proposal, and not a commitment to make this specific change.
The text was updated successfully, but these errors were encountered: