[GEN-2111]: read & display "conditions" for actions #2072
Merged
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.
This pull request includes several changes to the
frontend/graph
andfrontend/webapp
directories to introduce thePipelineAction
type and improve handling of conditions in the application. Below are the most important changes:GraphQL Schema and Resolvers:
Added
PipelineAction
type to replaceIcaInstanceResponse
in the GraphQL schema and resolvers. This new type includes anActionStatus
field with conditions. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]Introduced the
convertConditions
function infrontend/graph/conversions.go
to convert conditions from the API format to the model format.Web Application Components:
Updated the
ActionDrawer
component to displayConditionDetails
using the newPipelineAction
type. [1] [2] [3]Modified the
SourceDrawer
component to handle conditions more robustly and display them usingConditionDetails
. [1] [2]GraphQL Queries:
GET_COMPUTE_PLATFORM
query to include the newPipelineAction
type and itsstatus
field with conditions. [1] [2]Type Definitions:
PipelineAction
andCondition
types, ensuring proper handling of conditions in the application state. [1] [2] [3]