Add tools to ensure we didn't break API compatibility
@HaroldCindy is already working on this.
Since Nov 11, 2025.
Assessment
This issue has not been assessed yet.
Description
Now that we're better about making sure everything has a unique reference in Ares, we need to be sure that we don't accidentally remove anything from the API surface, and adding anything should increment the API version. We need some tooling to ensure that we do so. Might also be nice to be able to swap out function implementations depending on API version if necessary to help us avoid the ll.*Base64.*Correct() problem.
- Dominant language
- C++
- Stars
- 17
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 4
Contributor 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 secondlife/slua
-
documentation team:server
secondlife/slua#91 · 1 assignee ·
-
secondlife/slua#62 · 6 comments · 1 assignee ·
-
enhancement
secondlife/slua#25 · 1 assignee ·
-
enhancement
secondlife/slua#24 · 2 comments · 1 assignee ·
-
enhancement
secondlife/slua#19 · 1 assignee ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google/libultrahdr#485 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
godotengine/godot#123776 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 60/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ros2/common_interfaces#344 ·