You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a kRPC property which I marked as Obsolete.
[KRPCProperty, Obsolete("MyReason")]
public float MyProperty { get; set; }
However, the generated documentation does not take in account Obsolete annotation and does not warn users about deprecation. I know I can add XML comments but it would be nice to have the property grayed out (the background?).
Furthermore, this change is not reflected in generated client source files either. For example, in Java, it could utilize @Deprecated annotation. I think this would help users remove deprecated calls as soon as possible without having to read the documentation or the changelog, because their compiler would warn them about deprecation.
The text was updated successfully, but these errors were encountered:
I have a kRPC property which I marked as
Obsolete
.However, the generated documentation does not take in account
Obsolete
annotation and does not warn users about deprecation. I know I can add XML comments but it would be nice to have the property grayed out (the background?).Furthermore, this change is not reflected in generated client source files either. For example, in Java, it could utilize
@Deprecated
annotation. I think this would help users remove deprecated calls as soon as possible without having to read the documentation or the changelog, because their compiler would warn them about deprecation.The text was updated successfully, but these errors were encountered: