Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

The netstandard2.0 public surface and dependencies are checked by nothing

Abierto
  • ¿Algo no está bien?
#1,182 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp
Área
build-system, testing

Línea de trabajo

Comienza con Sources/AngouriMath/AngouriMath.csproj y la configuración del framework de destino de UnitTests; después, lee PublicApi.txt y KernelDependenciesTest para entender las comprobaciones actuales para un único TFM. Compara los legs de netstandard2.0 y de net actuales, usando EverythingBuild.yml como contexto. Se considera terminado cuando se comprueban la API pública y las dependencias del kernel de cada TFM seleccionado, con cobertura separada de PublicApi.txt.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

UnitTests targets net10.0 only, so everything asserted about the public surface and about the
kernel's dependencies is asserted about one of the three target frameworks.

Sources/AngouriMath/AngouriMath.csproj builds netstandard2.0;net8.0;net10.0, and the legs differ
by construction:

  • Core/Serialization is #if NET8_0_OR_GREATER
  • GenericMath is Compile Removed below net7
  • netstandard2.0 carries System.Memory as a package rather than a framework reference

So PublicApi.txt records the net10.0 surface, and the netstandard2.0 public surface is checked by
nothing. A member could be added to, or removed from, that leg without any test noticing.

This is #783's own objection — "unbuilt configurations rot silently" — arriving through the one
construct that issue permits. It closed as adopted; this is the piece it did not cover.

KernelDependenciesTest (#1181) has the same bound and says so in its own remarks: it asserts the
referenced assemblies of whichever framework UnitTests builds, which is why System.Memory appears
there as a framework reference and the netstandard2.0 package reference is invisible to it.

What would close this

A per-TFM check, and the cheap version is probably enough: multi-target UnitTests (or a small
second test project) at least across netstandard2.0 and the current net, and record one
PublicApi.txt per leg. That also gives KernelDependenciesTest its second column for free.

What is not being claimed

No defect has been observed on the netstandard2.0 leg. The point is that one could not be observed —
EverythingBuild.yml compiles it, which catches a build break, and nothing checks its surface or
its dependencies. Filed because two separate checks have now hit the same bound and both had to
record it as a limitation rather than test it.

Lenguaje dominante
C#
Estrellas
831
Forks
79
Merge medio
2 h 22 min
PR fusionados (30 d)
507

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ASC-Community/AngouriMath

Todos los issues de ASC-Community/AngouriMath

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.