Improve "Version Compatibility" section in "What is GDExtension" #10404
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dsnopek
added
enhancement
area:manual
tetrapod00
approved these changes
Dec 12, 2024
dsnopek
force-pushed
the
gdextension-version-compatibility
branch
from
ddd6e5d to
6582877
Compare
mhilbrunner
approved these changes
Dec 12, 2024
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This attempts to improve the "Version Compatibility" section on this page
There is a warning that talks about version compatibility at the top: in this PR, I've reduced that warning to just talk about how GDExtension is experimental, and moved the version compatibility details down into the "Verson Compatibility" section.
I also expanded a bit on the note about using engine builds with double precision floats, adding:
extension_api.json(which is something folks frequently miss), andextension_api.jsonanytime you're using a custom engine build (not just for double precision floats)