Skip to content

fix: reference to incorrect node when computing schema name of persisted call #646

fix: reference to incorrect node when computing schema name of persisted call

fix: reference to incorrect node when computing schema name of persisted call #646

Triggered via pull request June 11, 2024 13:06
Status Failure
Total duration 28s
Artifacts

ci.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors
Checks
Property 'expression' does not exist on type 'LeftHandSideExpression'.
Checks
Process completed with exit code 1.