Why is KubernetesDeserializer in a package named "internal"?

[seglo]

You must use KubernetesDeserializer.registerCustomKind in order to successfully watch CustomResourceDefinitions, as implemented in CRDExample. Yet this type is in a package named "internal". Does this imply it shouldn't be used by library users? Should it be moved?

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[rohanKanojia]

I think it won't be a problem if we move it out of internal package.

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[ps-19]

@rohanKanojia can i work on this issue. I am not being able to understand such a huge codebase where to start from.

[shawkins]

Looking at this again - from the original motivation and typical usage with fabric8 it no longer needs to be moved. If you are using the dsl, there's no need to manually call registerCustomKind.

The only reason you'd need to do that is if you are using deserialization routines independently of the dsl.