Is it possible to make this library trimmable by default

[albertwoo]

Description

I am using this library in blazor wasm application, but this library's bundle size is 1008kb which is a lot for a web application.
I also created similar ticket for FSharp.Data.Adaptive, which they already made it hanppen. fsprojects/FSharp.Data.Adaptive#104
And the result is pretty good.

Known workarounds

People can add below stuff to their own application to make it work. But it is better to have it support by default.

<Target Name="ConfigureTrimming" BeforeTargets="PrepareForILLink">
<ItemGroup>
	<ManagedAssemblyToLink Condition="'%(Filename)' == 'FSharp.Data'">
		<TrimMode>link</TrimMode>
		<IsTrimmable>true</IsTrimmable>
	</ManagedAssemblyToLink>
</ItemGroup>
</Target>

[cartermp]

This library does make a bit of use of reflection. I'm not sure what that means for trimmability.

[albertwoo]

Then below stuff should be able to add to the project file, so other people do not need to use the workaround.

<TrimMode>link</TrimMode>
<IsTrimmable>true</IsTrimmable>

[albertwoo]

Here is the docs: https://docs.microsoft.com/en-us/dotnet/core/deploying/trimming/prepare-libraries-for-trimming

[github-actions]

🤖 This is an automated response from Repo Assist.

Good question on trimmability — there's a meaningful distinction between FSharp.Data's design-time code (type provider infrastructure, runs in the IDE/compiler) and its runtime code (JSON/CSV/XML/HTML parsers, ships in the NuGet package to end users). For Blazor WASM, only the runtime assembly matters for trimming.

The challenge: The runtime helpers in FSharp.Data.dll do use reflection in a few places — notably the type provider plumbing (ProvidedTypes.fs) and some dynamic invocation in the generated accessor code. Adding (IsTrimmable)true(/IsTrimmable) without first auditing all reflection call sites and adding [(DynamicallyAccessedMembers)] annotations would cause trim warnings (or, in (TrimmerRootDescriptor)-enabled projects, silent failure at runtime).

Practical path forward:

1. Enable (IsTrimmable)true(/IsTrimmable) + (EnableTrimAnalyzer)true(/EnableTrimAnalyzer) in FSharp.Data.fsproj
2. Fix all resulting trim analysis warnings (add [(DynamicallyAccessedMembers(...))] to any Type parameters used reflectively)
3. Add a Blazor WASM smoke test to the CI to catch regressions

The FSharp.Data.Adaptive precedent you linked is encouraging — they're a simpler library without the type provider machinery, but the annotation approach is the same.

This is a good candidate for a contribution if anyone wants to pick it up. The trim analyser will guide you to exactly what needs annotating.

Generated by Repo Assist

To install this workflow, run gh aw add githubnext/agentics/workflows/repo-assist.md@de40494d3f62516449f458c4f8d8d2fe370708fe. View source at https://github.com/githubnext/agentics/tree/de40494d3f62516449f458c4f8d8d2fe370708fe/workflows/repo-assist.md.