fix: Unify version display for public and private designs #1081
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Notes for Reviewers
This PR fixes: https://github.com/layer5io/meshery-cloud/issues/3585
Reason
There are three relevant states for a design: private, public, and published. The
private
andpublic
states should both reflect the current draft's version number, which is stored in theversion
field. Only apublished
design should display thepublished_version
.The bug was that the UI was incorrectly displaying the
published_version
for designs that were set topublic
. This created problems:published_version
, the UI would show an incorrect fallback value (like0.0.0
or""
).published_version
, the UI would show an incorrect value.Fix
20250617_200454.mp4