Skip to content

move paths to an environment w/in envsetup#80

Merged
nicholas-masel merged 5 commits intodevelfrom
75-explore-options-other-than-attach
Jul 30, 2025
Merged

move paths to an environment w/in envsetup#80
nicholas-masel merged 5 commits intodevelfrom
75-explore-options-other-than-attach

Conversation

@nicholas-masel
Copy link
Copy Markdown
Collaborator

@nicholas-masel nicholas-masel commented Jul 9, 2025

Initial draft to move paths to an environment. I'll update the rest of the package (vignettes, etc.) after we agree this is the direction we want to go.

@nicholas-masel nicholas-masel linked an issue Jul 9, 2025 that may be closed by this pull request
@mstackhouse
Copy link
Copy Markdown
Contributor

Does the environment here live in the package namespace?

@nicholas-masel
Copy link
Copy Markdown
Collaborator Author

nicholas-masel commented Jul 9, 2025 via email

@nicholas-masel
Copy link
Copy Markdown
Collaborator Author

We could store all of the path objects in global too. I think the only benefit to putting this within the environment of the package is so they are not overwritten. And so we can have the read and write functions look directly here for these path objects.

@nicholas-masel nicholas-masel changed the base branch from main to devel July 17, 2025 17:29
@nicholas-masel nicholas-masel marked this pull request as ready for review July 18, 2025 13:53
@nicholas-masel nicholas-masel self-assigned this Jul 22, 2025
@nicholas-masel
Copy link
Copy Markdown
Collaborator Author

@mstackhouse I'll merge into dev and you can do the review of the PR to main.

@nicholas-masel nicholas-masel merged commit 39d772e into devel Jul 30, 2025
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Explore options other than attach() for paths

2 participants