Since we have incorporated custom Credo Checks into our template, we disable certain checks for several base files (created from mix / phoenix templates for example) because they don't follow our convention(s) fully. The root problem is to disable these checks the path for these specific files is read - which all of them may or may not exist depending on the project type selected for the template - and this can result in File not found error logs in the console.
Although this does not prevent the project creation or cause any issues, this may not be apparent to the users and is generally a negative experience.
Why
Since we have incorporated custom Credo
Checksinto our template, we disable certain checks for several base files (created from mix / phoenix templates for example) because they don't follow our convention(s) fully. The root problem is to disable these checks thepathfor these specific files is read - which all of them may or may not exist depending on the project type selected for the template - and this can result inFile not founderror logs in the console.Although this does not prevent the project creation or cause any issues, this may not be apparent to the users and is generally a negative experience.
Slack thread: https://nimble-co.slack.com/archives/C0112R61J3W/p1669093000523539
Who Benefits?
Any user of the template