Refine CEF installer artifact detection logic in app update process
All checks were successful
farmcontrol/farmcontrol-ui/pipeline/head This commit looks good
All checks were successful
farmcontrol/farmcontrol-ui/pipeline/head This commit looks good
- Updated isCefInstallerArtifact function to use a regex pattern for identifying CEF installer artifacts, improving accuracy in artifact name matching. - Enhanced comments for clarity on CEF build naming conventions, aiding future maintenance and understanding of the code.
This commit is contained in:
parent
1d741d8932
commit
e9f4c1f3d3
@ -27,7 +27,8 @@ const getArtifactName = (artifact) =>
|
|||||||
|
|
||||||
const isCefInstallerArtifact = (artifact) => {
|
const isCefInstallerArtifact = (artifact) => {
|
||||||
const name = getArtifactName(artifact).toLowerCase()
|
const name = getArtifactName(artifact).toLowerCase()
|
||||||
return name.endsWith('-cef.exe') || name.endsWith('-cef.pkg')
|
// CEF builds are named like farmcontrol-0.1.1-x64-cef.msi / -cef.pkg / -cef.exe
|
||||||
|
return /-cef\.[a-z0-9]+$/.test(name)
|
||||||
}
|
}
|
||||||
|
|
||||||
const normalizeArch = (arch) => {
|
const normalizeArch = (arch) => {
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user