The documentation referenced [DataSourceGeneratorProperty<T>] attribute for nested data source initialization, but this attribute doesn't exist in the codebase. Users trying to follow the documentation examples would encounter compilation errors.

Problem

The issue was reported in the nested data sources documentation at https://tunit.dev/docs/test-authoring/nested-data-sources where examples showed:

[DataSourceGeneratorProperty<RedisTestContainer>]
public required RedisTestContainer Redis { get; init; }

However, DataSourceGeneratorProperty is not implemented in TUnit.Core, causing compilation failures for users following the documentation.

Solution

Updated all documentation to use [ClassDataSource<T>] which is a real attribute that implements IDataSourceAttribute and supports property injection. The corrected pattern is:

[ClassDataSource<RedisTestContainer>]
public required RedisTestContainer Redis { get; init; }

Changes Made

• docs/docs/test-authoring/nested-data-sources.md: Replaced all instances of [DataSourceGeneratorProperty<T>] with [ClassDataSource<T>]
• docs/examples/nested-data-sources-example.md: Updated examples to use the correct attribute
• docs/examples/nested-data-sources-quickstart.md: Updated examples to use the correct attribute
• Updated explanatory text to mention "any attribute implementing IDataSourceAttribute" for broader applicability

Verification

• Build succeeds with no compilation errors
• Existing tests in PropertyDataSourceInjectionTests.cs confirm [ClassDataSource<T>] works correctly for property injection
• No remaining references to the non-existent attribute in the documentation

Users can now successfully follow the documentation examples for nested data source initialization.

Fixes #2928.

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.