Skip to content

Modify markup tag interfaces and fix some bugs #12557

Modify markup tag interfaces and fix some bugs

Modify markup tag interfaces and fix some bugs #12557

Triggered via pull request September 16, 2024 04:42
Status Success
Total duration 10m 14s
Artifacts

test-content.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected], actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build
'EntitySystem.TryGet<T>(out T?)' is obsolete: 'Either use a dependency, resolve and cache IEntityManager manually, or use EntityManager.System<T>()'
build
'BoundUserInterface.DeferredClose' is obsolete
build
'BoundUserInterface.DeferredClose' is obsolete
build
'BoundUserInterface.DeferredClose' is obsolete
build
The variable 'defaultErrorOccurred' is assigned but its value is never used
build
'IComponent.Owner' is obsolete: 'Update your API to allow accessing Owner through other means'
build
'Component.Owner' is obsolete: 'Update your API to allow accessing Owner through other means'
build
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.