Make implicit conversion more flexible
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- compilers
Research direction
The payload names no files or functions, so first find where implicit conversion between two types is currently decided as a true/false check in the typir sources. Read how that result is consumed by callers before changing its shape. Done means the conversion result can express the three states from the issue (no, with data loss, without data loss) while existing boolean callers keep working, and the test suite still passes. Agree the API shape with the maintainers first, since the issue sets no design.
Written by the indexing model from the issue text.
Description
At the moment, implicit conversion between two types is possible or not (true | false). Sometimes it is necessary to support implicit conversion with e.g. data loss as well (no | with_data_loss | without_data_loss).
- Dominant language
- TypeScript
- Stars
- 52
- Forks
- 5
- Avg merge
- 1h 31m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TypeFox/typir
-
Difficulty 3/5 Half a day Newbie friendliness 22/100
-
Infrastructure
Difficulty 5/5 Over a week Newbie friendliness 12/100
-
Infrastructure
Difficulty 5/5 Over a week Newbie friendliness 12/100
-
Predefined Types
Difficulty 5/5 Over a week Newbie friendliness 12/100
-
Predefined Types
Difficulty 4/5 3-5 days Newbie friendliness 18/100
Similar issues
-
Autocomplete still accepts an option after becoming disabledPossibly taken @Xapollon430 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
reduxjs/react-redux#2416 · 1 comment ·