- differentiate between configuration not found vs configuration could not be parsed

- help with https://github.com/mikepenz/release-changelog-builder-action/issues/147
This commit is contained in:
Mike Penz
2021-01-05 18:30:26 +01:00
parent 97c40aa8d5
commit 1f2d0ea832
+13 -6
View File
@@ -51,11 +51,7 @@ export function resolveConfiguration(
)
core.debug(`configurationPath = '${configurationPath}'`)
const providedConfiguration = readConfiguration(configurationPath)
if (!providedConfiguration) {
core.info(
`⚠️ Configuration provided, but it couldn't be found, or failed to parse. Fallback to Defaults`
)
} else {
if (providedConfiguration) {
configuration = providedConfiguration
}
}
@@ -66,11 +62,22 @@ export function resolveConfiguration(
* Reads in the configuration from the JSON file
*/
function readConfiguration(filename: string): Configuration | null {
let rawdata: string
try {
rawdata = fs.readFileSync(filename, 'utf8')
} catch (error) {
core.info(
`⚠️ Configuration provided, but it couldn't be found. Fallback to Defaults.`
)
return null
}
try {
const rawdata = fs.readFileSync(filename, 'utf8')
const configurationJSON: Configuration = JSON.parse(rawdata)
return configurationJSON
} catch (error) {
core.info(
`⚠️ Configuration provided, but it couldn't be parsed. Fallback to Defaults.`
)
return null
}
}