feat: marking public APIs with annotations#3428
Conversation
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
…3263) Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
…does not have to be Kubernetes resources (operator-framework#3377) Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
…y deadline (operator-framework#3380) Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
xstefank
left a comment
There was a problem hiding this comment.
As we discussed on the meeting, I don't think introducing this kind of new API that we would need to continuously maitain would add much better approach of what is public and what is not. We should have a clearly defined rules, but users will not check this and we would need to remember to take care of keeping all annotations in check.
I'm also not fully convinced TBH either, will come back to this a bit later. Also we can discuss more in community calls. |
No description provided.