Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Breaking change] Strongly typed API or not ?

Open
#180 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
react
Domain
frontend

Research direction

Start by reviewing the breaking changes introduced in the last minor version and the current Fable.React API. The issue does not name files or tests, so first map the typed and untyped concepts involved, then clarify the proposed direction and how SSR should be supported. Done requires an agreed API approach rather than a small isolated edit.

Written by the indexing model from the issue text.

Description

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.

Dominant language
F#
Stars
277
Forks
65
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fable-compiler/fable-react

All issues in fable-compiler/fable-react

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.