Add support for computed properties

[ngelotte]

I use a few calculated properties on the Class that is being export to Typescript and the properties do show up on the Javascript object but they are not shown in the Interface that is generated by Typescript. Which makes it harder to work with in a typescript environment because it keeps saying that it does not exist on the type. So you have to create a manual interface in typescript or do casting to get around it.

For example:

C#
public class SalesItem
{
public decimal Qty { get; set; }
public decimal Amount { get; set; }
public decimal Total => Qty * Amount;
}

Emited Typescript
export interface SalesItem{
qty : number;
amount: number;
}

Expected emitted Typescript
export interface SalesItem{
qty : number;
amount: number;
total: number;
}

Maybe there is already an attribute or something but I could not find it in the docs.

Thanks again for making this library. I am integrating it into our first internalapp and it has allowed us to share some complicated code between the front and backend quite easily.

[elringus]

Computed properties are not supported yet. I'm actually confused how they showed up on the JS proxies at all, as I don't remember implementing any support for this. Will keep this as a feature request. Thanks for the feedback!

[ngelotte]

There is not a perfect match because once you leave the c# environment the calculations will stop happening. But you could make it a readonly property which seems like a close enough match.

[elringus]

Just to be clear, this is only considered for the interface/byref proxies. Data types with value semantics (structs and records) won't have this. If you're using SalesItem as a means to transfer readonly data, this is not something Bootsharp supports. It has to be a struct or a record.

[ngelotte]

That makes sense. I am using a Class and expecting most of it's properties to be mutable. I am fine with the calculated properties just becoming normal properties as well. The Readonly attribute just seemed like a little better fit because changes to those properties will be ignored if passed back into the c# method because they have no where to get saved when they get serialized back from Json.