Skip to content

fix: use destination definition name in place of string for custom object #2651

fix: use destination definition name in place of string for custom object

fix: use destination definition name in place of string for custom object #2651

Triggered via pull request September 20, 2024 05:36
Status Success
Total duration 3m 40s
Artifacts

component-test-report.yml

on: pull_request
test_and_upload
3m 29s
test_and_upload
Fit to window
Zoom out
Zoom in