'SearchViewModel' does not contain a definition for 'Spell' and no accessible extension method 'Spell' accepting a first argument of type 'SearchViewModel' could be found (are you missing a using directive or an assembly reference?)

'SearchCatalogueViewModel' does not contain a definition for 'Spell' and no accessible extension method 'Spell' accepting a first argument of type 'SearchCatalogueViewModel' could be found (are you missing a using directive or an assembly reference?)

'SearchViewModel' does not contain a definition for 'Spell' and no accessible extension method 'Spell' accepting a first argument of type 'SearchViewModel' could be found (are you missing a using directive or an assembly reference?)

'SearchViewModel' does not contain a definition for 'Spell' and no accessible extension method 'Spell' accepting a first argument of type 'SearchViewModel' could be found (are you missing a using directive or an assembly reference?)

'SearchCatalogueViewModel' does not contain a definition for 'Spell' and no accessible extension method 'Spell' accepting a first argument of type 'SearchCatalogueViewModel' could be found (are you missing a using directive or an assembly reference?)

'SearchCatalogueViewModel' does not contain a definition for 'Spell' and no accessible extension method 'Spell' accepting a first argument of type 'SearchCatalogueViewModel' could be found (are you missing a using directive or an assembly reference?)

'SearchViewModel' does not contain a definition for 'Spell' and no accessible extension method 'Spell' accepting a first argument of type 'SearchViewModel' could be found (are you missing a using directive or an assembly reference?)

'SearchCatalogueViewModel' does not contain a definition for 'Spell' and no accessible extension method 'Spell' accepting a first argument of type 'SearchCatalogueViewModel' could be found (are you missing a using directive or an assembly reference?)

'SearchViewModel' does not contain a definition for 'Spell' and no accessible extension method 'Spell' accepting a first argument of type 'SearchViewModel' could be found (are you missing a using directive or an assembly reference?)

'SearchViewModel' does not contain a definition for 'Spell' and no accessible extension method 'Spell' accepting a first argument of type 'SearchViewModel' could be found (are you missing a using directive or an assembly reference?)

The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3, microsoft/[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/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

XML comment has syntactically incorrect cref attribute 'Task{ResourceVersionEventViewModel}}'

XML comment has syntactically incorrect cref attribute 'Task{List{ResourceVersionValidationResultViewModel}}'

XML comment has syntactically incorrect cref attribute 'Action{string}'

XML comment has syntactically incorrect cref attribute 'Task{PagedResultSet{UserLearningRecordViewModel}}'

Type parameter declaration must be an identifier not a type. See also error CS0081.

Type parameter declaration must be an identifier not a type. See also error CS0081.

Type parameter declaration must be an identifier not a type. See also error CS0081.

XML comment has syntactically incorrect cref attribute 'Task{PagedResultSet{UserLearningRecordViewModel}}'

Type parameter declaration must be an identifier not a type. See also error CS0081.

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.

Unexpected input(s) 'npm', valid inputs are ['always-auth', 'node-version', 'node-version-file', 'architecture', 'check-latest', 'registry-url', 'scope', 'token', 'cache', 'cache-dependency-path']