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
As we begin to refactor and change some of our Archetypes it will be helpful to go through a 1-release deprecation cycle on things that would otherwise break user API usage.
When an existing archetype is being deprecated we should be able to apply a deprecated attribute to the archetype definition and code-gen deprecation notices for the Archetype constructors across all 3 languages.
In the future we should also be able to deprecate usage of individual component-fields within an archetype, but this will be a bit more involved and not needed immediately.
The deprecated attribute should be a string with a message that can explain to users what to do, such as: "This archetype has been replaced by the new archetypes: Scalar and SeriesStyle"
As we begin to refactor and change some of our Archetypes it will be helpful to go through a 1-release deprecation cycle on things that would otherwise break user API usage.
When an existing archetype is being deprecated we should be able to apply a deprecated attribute to the archetype definition and code-gen deprecation notices for the Archetype constructors across all 3 languages.
In the future we should also be able to deprecate usage of individual component-fields within an archetype, but this will be a bit more involved and not needed immediately.
The deprecated attribute should be a string with a message that can explain to users what to do, such as: "This archetype has been replaced by the new archetypes: Scalar and SeriesStyle"
Python
In python we should follow the pattern established in: https://github.com/rerun-io/rerun/pull/3564/files
@deprecated
decorator to the classC++
TODO
Rust
TODO
The text was updated successfully, but these errors were encountered: