From 1695ac05f0c6364503a936c384fb67305215bc35 Mon Sep 17 00:00:00 2001 From: Paul Irwin Date: Fri, 11 Oct 2024 17:14:39 -0600 Subject: [PATCH] Add back RandomExtensions to TestFramework docs, Fix note formatting on OpenNLP docs --- src/Lucene.Net.Analysis.OpenNLP/overview.md | 3 ++- websites/apidocs/filterConfig.yml | 3 --- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/src/Lucene.Net.Analysis.OpenNLP/overview.md b/src/Lucene.Net.Analysis.OpenNLP/overview.md index 1667c7f52e..44c2c352f2 100644 --- a/src/Lucene.Net.Analysis.OpenNLP/overview.md +++ b/src/Lucene.Net.Analysis.OpenNLP/overview.md @@ -46,7 +46,8 @@ When a `` is included for this NuGet package in your SDK-style The `` item group operates similar to a dependency in Maven. All transitive dependencies are collected and resolved, and then the final output is produced. However, unlike `PackageReference`s, `MavenReference`s are collected by the final output project, and reassessed. That is, each dependent Project within your .NET SDK-style solution contributes its `MavenReference`s to project(s) which include it, and each project makes its own dependency graph. Projects do not contribute their final built assemblies up. They only contribute their dependencies. Allowing each project in a complicated solution to make its own local conflict resolution attempt. -> **NOTE** `` is only supported on SDK-style MSBuild projects. +> [!NOTE] +> `` is only supported on SDK-style MSBuild projects. ## MavenReference Example diff --git a/websites/apidocs/filterConfig.yml b/websites/apidocs/filterConfig.yml index 92f3472371..02b8657ab1 100644 --- a/websites/apidocs/filterConfig.yml +++ b/websites/apidocs/filterConfig.yml @@ -5,6 +5,3 @@ apiRules: - exclude: uidRegex: ^Lucene\.Net\.Test$ type: Namespace -- exclude: - uidRegex: ^Lucene\.Net\.RandomExtensions$ - type: Class