Fix/configuration component content type · Kentico/xperience-by-kentico-lucene@74a583e

Triggered via pull request April 8, 2024 14:21

bkapustik

synchronize #42

Status Success

Total duration 1m 23s

Artifacts –

ci.yml

on: pull_request

9 warnings

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

build: examples/DancingGoat/Models/Reusable/Cafe/CafeViewModel.cs#L8

XML comment has badly formed XML -- 'A string literal was expected, but no opening quotation mark was found.'

build: examples/DancingGoat/Models/WebPage/ArticlesSection/ArticlesSectionViewModel.cs#L15

XML comment has badly formed XML -- 'A string literal was expected, but no opening quotation mark was found.'

build: examples/DancingGoat/Models/ContentRepositoryBase.cs#L30

XML comment has a param tag for 'pageRetriever', but there is no parameter by that name

build: examples/DancingGoat/Models/WebPage/SEOSchemaDataRetriever.cs#L85

XML comment has cref attribute 'SEOAllowSearchIndexing' that could not be resolved

build: examples/DancingGoat/Models/Reusable/Cafe/CafeViewModel.cs#L8

XML comment has badly formed XML -- 'A string literal was expected, but no opening quotation mark was found.'

build: examples/DancingGoat/Models/WebPage/ArticlesSection/ArticlesSectionViewModel.cs#L15

XML comment has badly formed XML -- 'A string literal was expected, but no opening quotation mark was found.'

build: examples/DancingGoat/Models/ContentRepositoryBase.cs#L30

XML comment has a param tag for 'pageRetriever', but there is no parameter by that name

build: examples/DancingGoat/Models/WebPage/SEOSchemaDataRetriever.cs#L85

XML comment has cref attribute 'SEOAllowSearchIndexing' that could not be resolved