Fix/configuration component content type #140
Annotations
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 Solution:
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 Solution:
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 Solution:
examples/DancingGoat/Models/ContentRepositoryBase.cs#L30
XML comment has a param tag for 'pageRetriever', but there is no parameter by that name
|
|
Build Solution:
examples/DancingGoat/Models/WebPage/SEOSchemaDataRetriever.cs#L85
XML comment has cref attribute 'SEOAllowSearchIndexing' that could not be resolved
|
|
Build Solution:
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 Solution:
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 Solution:
examples/DancingGoat/Models/ContentRepositoryBase.cs#L30
XML comment has a param tag for 'pageRetriever', but there is no parameter by that name
|
|
Build Solution:
examples/DancingGoat/Models/WebPage/SEOSchemaDataRetriever.cs#L85
XML comment has cref attribute 'SEOAllowSearchIndexing' that could not be resolved
|
Loading