Fix: YAML workflow list UI now only shows 'No description'#585
Open
LaansDole wants to merge 2 commits intoOpenBMB:mainfrom
Open
Fix: YAML workflow list UI now only shows 'No description'#585LaansDole wants to merge 2 commits intoOpenBMB:mainfrom
LaansDole wants to merge 2 commits intoOpenBMB:mainfrom
Conversation
Collaborator
|
Hello, I didn't notice the bug displayed on the front-end page. Could you please provide a screenshot to illustrate it? |
Contributor
Author
|
So I was fixing this from the latest changes, @zxrys: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Problem
The workflow list UI always shows "No description" due to a frontend–backend contract mismatc
The backend
/descendpoint returns{ "description": "..." }, but the frontend readsfileData.content(expecting raw YAML) and tries to re-parse it client-side. SincefileData.contentis undefined, parsing always fails and the catch block returns "No description".