search

fable-compiler / fable-react

Fable bindings and helpers for React and React Native
MIT License
275 stars 66 forks source link

[Breaking change] Strongly typed API or not ? #180

Open MangelMaxime opened 5 years ago

MangelMaxime commented 5 years ago

The last minor version of Fable.React introduced several breaking changes.

From a user perspective, this is not really friendly so I think it is time to decide if we want to fully type the API or no :)

Because nowadays, my user code looks like a mismatch between several concepts. I can take the subject to explore typed API if this is the way to go. And make it works with SSR etc.

Luiz-Monad commented 5 years ago

I saw this, it was easy to fix, just replace some "strings" with the new enums. But as I was updating everything to the bleeding edge, I kind of expected it. I guess we could type all the CSS properties and then release a major version, breaking changes in the minor version breaks the Semantic Versioning, it's not nice.

MangelMaxime commented 5 years ago

I guess we could type all the CSS properties and then release a major version, breaking changes in the minor version breaks the Semantic Versioning, it's not nice.

Yes, I want to avoid this situation