-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate rjournal_article()
in favor of **rjtools** ?
#522
Comments
@dicook @mitchelloharawild what are your thoughts on this, considering rjtools seems to be the recommended way now ? |
Definitely would vote “yes"
On 2 May 2023, at 7:13 pm, Christophe Dervieux ***@***.***> wrote:
@dicook @mitchelloharawild what are your thoughts on this, considering rjtools seems to be the recommended way now ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
cheers,
Di
…---
Dianne Cook
***@***.***
|
I have done it in #531 - basically it will produce a warning when |
This old thread has been automatically locked. If you think you have found something related to this, please open a new issue by following the issue guide (https://yihui.org/issue/), and link to this old issue if necessary. |
Hi !
@mitchelloharawild I did the update of #517 based on rjtools bundled file.
In rjournal/rjtools#61 (comment) you raise the good question of
rjournal_article()
future now that rjtools exists. But you never opened an issue in this repo to ask hereI am ok with adding a deprecation warning inside rticles package to explain that now rjtools should be used. Initially we did the format as there was none, there is no point in keeping it inside rticles if it is not to be used to submit to R Journal
What should we do about this ?
Originally posted by @cderv in #517 (comment)
The text was updated successfully, but these errors were encountered: