LiveSplit / LiveSplit/livesplit-core
Ensure proper handling of Nullable Strings in C API
- Dominant language
- Rust
- Stars
- 227
- Forks
- 81
- Avg merge
- 22h 45m
- Merged PRs (30d)
- 3
Description
Seems like we don't properly handle this in most of the language bindings.
Languages to check / fix:
Output:
- [x] ~~JavaScript / TypeScript for emscripten~~
- [x] JavaScript / TypeScript for Node
- [x] JavaScript / TypeScript for WASM
- [x] C#
- [ ] Java JNA
- [ ] Java JNI
- [ ] Kotlin JNI
- [ ] Swift
- [ ] Ruby
- [x] Python
Input (apparently we have no function that takes a nullable string as input atm):
- [x] ~~JavaScript / TypeScript for emscripten~~
- [ ] JavaScript / TypeScript for Node
- [ ] JavaScript / TypeScript for WASM
- [ ] C#
- [ ] Java JNA
- [ ] Java JNI
- [ ] Kotlin JNI
- [ ] Swift
- [ ] Ruby
- [ ] Python
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by auditing the language bindings listed in the issue, comparing the completed output entries with the unchecked output and input entries. Done means nullable strings are handled correctly for every listed binding, with coverage for both output and input where applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, csharp, java, javascript, kotlin, node.js, python, ruby, rust, swift, typescript, wasm
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100