Skipped internal properties on InvokeAsync<T> calls

[msynk]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

The internal properties are getting skipped/ignored on calls to InvokeAsync of JS interop calls.

for example:

public class Bounds
{
    public double Width { get; set; }
    internal double Height { get; set; }
}

function getBoundingClientRect(element) {
    const bounds = element.getBoundingClientRect();
    return {
        width: bounds.width,
        height: bounds.height
    };
}

you can see the problem in the result of the following line:

var bounds = await js.InvokeAsync<Bounds>("getBoundingClientRect", element);

---

It's probably because of the limitations of the STJ (discussed here: dotnet/runtime#31511) or something similar, but to be more clear it is a blocking issue for assemblies that don't want to expose their internal types to the outside world.
Btw, I can bypass this issue by making the type itself Internal and changing the properties access modifier to public.

Expected Behavior

The internal properties should receive their corresponding values from js interop calls.

Steps To Reproduce

you can see this problem in action in this repo:

https://github.com/msynk/blazor-internal-props-skip-invokeasync

it has both Blazor Server and Wasm.

Exceptions (if any)

No response

.NET Version

6.0.302

Anything else?

No response

[javiercn]

@msynk thanks for contacting us.

This is by design. The data gets serialized under the hood using System.Text.Json and that does not serialize internal properties. You can write a custom converter to change that. In addition to that, if you trim the app during publish and the property is not used elsewhere, the trimmer might not infer its usage and remove it.

[msynk]

@msynk thanks for contacting us.

This is by design. The data gets serialized under the hood using System.Text.Json and that does not serialize internal properties. You can write a custom converter to change that. In addition to that, if you trim the app during publish and the property is not used elsewhere, the trimmer might not infer its usage and remove it.

@javiercn thank you for your response.

I've already mentioned in the issue's body that it might be because of the limitation of the STJ and the GitHub issue discussing this limitation, and also a possible workaround (making the type itself internal).
it seems you didn't read the issue completely and missed that paragraph 😕

the feature required to resolve such a problem is planned for dotnet 8.0 now, so we need to wait until next year :(
meanwhile, we need to stick to the converter solution or make only the type internal.

[ghost]

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.