Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
I icoads.utils
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • brivas
  • icoads.utils
  • Issues
  • #3

Closed
Open
Created Jun 29, 2020 by brivas@brecinosrivasMaintainer

questions for Richard:

  1. Do you have to be super specific on each element of the documentation for the package function to be built correctly. Can you ignore all these aspects and still mange to create the function?

For example yours have this: read_imma.R#L70-91

Do you think that might be the problem? since my intention here is not to document all the functions from Liz but to have tool to export them and import them faster without sourcing code with file paths.

  1. How do you import functions from within the package that we are creating? I have added a #' @include id_group_func.R at the beginning of the scripts, I am not sure if is better to called them with my_package_name:: even if they are defined in the same package that I am creating?

Thanks

Edited Jun 29, 2020 by brivas
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking