Should we deprecate_warn Ergast functions? Not because they'll all be replaced, but to warn folks that the current package version likely won't work in a year? Once FastF1 gets their Ergast backend up and running we can convert to that API, and remove the depreciation warning.
Should we
deprecate_warn
Ergast functions? Not because they'll all be replaced, but to warn folks that the current package version likely won't work in a year? Once FastF1 gets their Ergast backend up and running we can convert to that API, and remove the depreciation warning.Originally posted by @pbulsink in https://github.com/SCasanova/f1dataR/discussions/207#discussioncomment-8264943