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
Throwing a warning at this stage after several months feels a bit confusing/pedantic. I worry it will cause more confusion than necessary.
I agree that hard or even soft deprecation that throws a warning at top-level might cause more harm than good, but you could document it as deprecated (as opposed to the current labeling as equal alternative), I believe that would make the use of ggraster easier to learn and teach in the long run.
The text was updated successfully, but these errors were encountered:
you could document it as deprecated (as opposed to the current labeling as equal alternative), I believe that would make the use of ggraster easier to learn and teach in the long run.
It's a nice suggestion, but I think the current setup is the best of all worlds.
I do see where you're coming from of course. Besides mentioning this in the README and vignettes however, I don't see a better way to "deprecate" in this case. .Deprecated() is simply too strong.
In #21 (comment)_ @evanbiederstedt wrote:
I agree that hard or even soft deprecation that throws a warning at top-level might cause more harm than good, but you could document it as deprecated (as opposed to the current labeling as equal alternative), I believe that would make the use of
ggraster
easier to learn and teach in the long run.The text was updated successfully, but these errors were encountered: