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
It seems that minimist is providing default values for some options that are not always the same as what the defaults are for prettier. This becomes an issue when trying to using a prettier config file that only specifies some options, but expects to fall back to prettier's defaults for others. This is because currently, when using the file-override config preference, the default values from minimist are being overridden by the resolved prettier config, but resolveConfig only returns what it finds in a config file, and does not have keys for any default options.
The text was updated successfully, but these errors were encountered:
It seems that minimist is providing default values for some options that are not always the same as what the defaults are for prettier. This becomes an issue when trying to using a prettier config file that only specifies some options, but expects to fall back to prettier's defaults for others. This is because currently, when using the
file-override
config preference, the default values from minimist are being overridden by the resolved prettier config, butresolveConfig
only returns what it finds in a config file, and does not have keys for any default options.The text was updated successfully, but these errors were encountered: