[bug]: front end versioning display discrepancy when there's a leading 0 of minor version number

[stupleb]

Prerequisites

• I have searched for existing issues that already report this problem.

Server Hardware

All

StartOS Version

0.3.5.1

Client OS

MacOS

Client OS Version

N/A

Browser

Firefox

Browser Version

N/A

Current Behavior

Leading zeros are displayed in some locations in StartOS, but not in some others. The lack of consistency means that at a glance the versions feel very distinct.

Expected Behavior

Display consistently.

Steps to Reproduce

Install a service
Install another that has the first as a dependency

Anything else?

No response

[MattDHill]

@dr-bonez code to display version below.

export function displayEmver(version: string): string {
  const vs = version.split('.')
  if (vs.length === 4) return `${vs[0]}.${vs[1]}.${vs[2]}~${vs[3]}`
  return version
}

Clams manifest looks correct: https://github.com/clams-tech/clams-remote-startos/blob/master/manifest.yaml#L103

The leading "0" appears to be srtipped before reaching the FE.

[dr-bonez]

The current emver specification doesn't actually support leading zeros, so it's stripped when the version is parsed. This will be accounted for in the new specification.

[MattDHill]

Leading zeros will not be supported by exver. The discrepancy shown in the image above will be resolved by neither having a leading zero. This means the upstream version of a package may look differently than otherise published by that team, but semantically it will behave the same.