Skip to content
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

Decide on what functions should be exported #46

Closed
seabbs opened this issue Feb 19, 2024 · 0 comments · Fixed by #47
Closed

Decide on what functions should be exported #46

seabbs opened this issue Feb 19, 2024 · 0 comments · Fixed by #47
Assignees
Labels

Comments

@seabbs
Copy link
Collaborator

seabbs commented Feb 19, 2024

As per the title we need to decide which functions should be exported (i.e. are designed to be used by a module user vs inside the module). We should also decide on a naming scheme for internal methods and check that all current code works as expected when these are not exported.

This issue was based on discussion in #40 where it was noted that several of the functions appeared to be for internal use only but were still being exported (i.e. we had a by default export all policy).

@SamuelBrand1 SamuelBrand1 self-assigned this Feb 19, 2024
@SamuelBrand1 SamuelBrand1 linked a pull request Feb 19, 2024 that will close this issue
@seabbs seabbs added this to the EpiAware 0.1.0 milestone Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants