search

EDIorg / EMLassemblyline

R package for creating EML metadata
https://ediorg.github.io/EMLassemblyline/
MIT License
28 stars 13 forks source link

How can issues() content be reset ? #79

Closed earnaud closed 3 years ago

earnaud commented 3 years ago

I am having some troubles with the issues() function. At the start of MetaShARK, it appears to be already filled.

Thanks by advance.

earnaud commented 3 years ago

I guess template_issues variable has something to see with it?

earnaud commented 3 years ago

Ok, I got it: template_issues is located in the .GlobalEnv(). I would recommend using the R options() to set an env in which to store template_issues(), with .GlobalEnv as a default. This would allow 1/ to avoid residual variables after running a script and 2/ better shiny app access to this issue management facility.

clnsmth commented 3 years ago

Good sleuthing Elie! Would you mind putting together a Paul request for this feature?

On Mon, Nov 23, 2020 at 06:55 earnaud notifications@github.com wrote:

Ok, I got it: template_issues is located in the .GlobalEnv(). I would recommend using the R options() to set an env in which to store template_issues(), with .GlobalEnv as a default. This would allow 1/ to avoid residual variables after running a script and 2/ better shiny app access to this issue management facility.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/EDIorg/EMLassemblyline/issues/79#issuecomment-732212440, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGCPUZI4YOVYXUPJRPAVXQDSRJZU5ANCNFSM4T7QYEWA .