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
Noticed something that may help the development of this package. Did not find that in the closed or open tickets.
The following code should be self explanatory
library(conflicted)
conflicts_prefer(config::get)
get
The result of the following is "<environment: namespace:base>" for the usage of "get" since the library "config" was never loaded. This may create unexpected behaviour without a warning like "warning: usage of a function from a different library than the preferred one: base::get instead of config::get"
I do not know if this is possible, or in the scope of the development plan of the conflicted library, but I think it could be a great improvement.
The text was updated successfully, but these errors were encountered:
Hi there,
Noticed something that may help the development of this package. Did not find that in the closed or open tickets.
The following code should be self explanatory
The result of the following is "<environment: namespace:base>" for the usage of "get" since the library "config" was never loaded. This may create unexpected behaviour without a warning like "warning: usage of a function from a different library than the preferred one: base::get instead of config::get"
I do not know if this is possible, or in the scope of the development plan of the conflicted library, but I think it could be a great improvement.
The text was updated successfully, but these errors were encountered: