dotnet / dotnet/dotnet-api-docs

Should mention differentiation between property schema changes and item data changes

Abierto
#1,908 0 comentarios 0 reacciones 0 asignados Ver en GitHub
area-System.ComponentModel dotnet-api/prod Pri2 untriaged
Lenguaje dominante
C#
Estrellas
949
Forks
1.7k
Merge medio
3 d 27 min
PR fusionados (30 d)
49

Descripción

The constructor with a propertychanged mentions that it should only be used for object schema changes and with adequate `ListChangedType` value.

This is in contrast to item changes, which specify item indices and different `ListChangedType` values.

The remarks section on this type, `ListChangedEventArgs`, should mention and describe this differentiation.

Furthermore, it is unclear how a combination of the two should be handled. The `ListChangedType` can not be combined, but constructors with both types of parameters imply this is somehow possible and intended, but they do not document how it's supposed to work/be handled.

---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: 97c8c9f6-72f6-2fb9-feed-d9a0bfb6348f
* Version Independent ID: 72c6439d-375b-e584-fd70-593411554e41
* Content: [ListChangedEventArgs Class (System.ComponentModel)](https://docs.microsoft.com/en-us/dotnet/api/system.componentmodel.listchangedeventargs?view=netframework-4.7.2)
* Content Source: [xml/System.ComponentModel/ListChangedEventArgs.xml](https://github.com/dotnet/dotnet-api-docs/blob/master/xml/System.ComponentModel/ListChangedEventArgs.xml)
* Product: **dotnet-api**
* GitHub Login: @dotnet-bot
* Microsoft Alias: **dotnetcontent**

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Start with xml/System.ComponentModel/ListChangedEventArgs.xml and its constructors and remarks, then review the referenced ListChangedType documentation to establish the distinction between property-schema and item-data changes. Done means the remarks clearly explain both cases and how constructor arguments should be handled together.

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

Evaluación

Stack tecnológico
csharp
Área
documentation
Tipo de issue
Documentación
Dificultad
2/5
Tiempo estimado
1-3 horas
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
42/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.