Fix #3149: Allow kOS users to read the non-gui KSPField properties #3150
+102
−12
Conversation
This file contains hidden or 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
AntonKuzin
commented
Oct 17, 2025
AntonKuzin
commented
Oct 20, 2025
added 6 commits
October 20, 2025 19:53
…thods using function overload to avoid unnecessary changes in the child classes
AntonKuzin
commented
Oct 21, 2025
Contributor
Author
There was a problem hiding this comment.
This is a draft version of the changes required for the docs(as I see it). I didn't built it, since they would probably still require some polishing from you because I'm not a native english speaker.
JonnyOThan
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I think it would be helpful to allow users to get(but not set) fields which are not accessible via UI. Related issue #3149
This is not a final PR, just something to start with.