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

Why is int32ToString needed for numeric props? (SolidJs)

Open
#3 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
fsharp
Domain
frontend

Research direction

Start with src/Feliz.JSX.Solid/Attribute.fs around line 1379 and reproduce the behavior using the linked Solid playground. Compare the generated handling of numeric props with SolidJS expectations; done means the reason for int32ToString is documented or the unnecessary conversion is removed with a regression check.

Written by the indexing model from the issue text.

Description

Why is int32ToString needed for numeric props? (SolidJs)

Doesn't Solid work well directly with numeric values in props ?

e.g. Attr.x1

test: https://playground.solidjs.com/anonymous/7523d6dc-9e88-43ab-a493-5421c9482aa4

Dominant language
F#
Stars
34
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.