fable-compiler / fable-react-native

Fable bindings and helpers for React Native projects
Apache License 2.0
49 stars 11 forks source link

Fable 4 incompatibility #68

Closed playfulThinking closed 8 months ago

playfulThinking commented 8 months ago

I updated a very simple project to Fable 4 and got this:

./src/fable_modules/Fable.React.Native.3.0.0-alpha001/Fable.ReactNative.Types.fs(1451,76): (1451,78) error FSHARP: The type parameter 'T is not defined. (code 39)
./src/fable_modules/Fable.React.Native.3.0.0-alpha001/Fable.ReactNative.Types.fs(1452,65): (1452,67) error FSHARP: The type parameter 'T is not defined. (code 39)

These are the lines that offend:

abstract getRowData: (obj -> U2<float, string> -> U2<float, string> -> 'T) option with get, set
abstract getSectionHeaderData: (obj -> U2<float, string> -> 'T) option with get, set

This seems to be related to this: https://github.com/fable-compiler/Fable/issues/3248 Apparently this is not a compiler error, but an illegal construction the CLR.

I don't know what these functions do, nor how to fix the declarations. Anybody?

Thanks much!

MangelMaxime commented 8 months ago

Hello @fremontmj,

It seemed like the package was already fixed in the Github repository but not published yet.

I just released version 4.0.0, please give it a try.

playfulThinking commented 8 months ago

Thank you, I will!

On Thu, Nov 9, 2023 at 11:54 AM Maxime Mangel @.***> wrote:

Hello @fremontmj https://github.com/fremontmj,

It seemed like the package was already fixed in the Github repository but not published yet.

I just released version 4.0.0, please give it a try.

— Reply to this email directly, view it on GitHub https://github.com/fable-compiler/fable-react-native/issues/68#issuecomment-1804552212, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAL4YZSR7VWKN4W66SBIRUDYDUYG5AVCNFSM6AAAAAA7AJBWPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBUGU2TEMRRGI . You are receiving this because you were mentioned.Message ID: @.***>

MangelMaxime commented 8 months ago

I am closing the issue but feel free to re-open if needed