Is your feature request related to a problem? Please describe.
I'm often frustrated when I want to write tests for internal helper functions but can't access them due to module encapsulation. This forces me to either expose functions I don't want to make part of the public API, give up on testing the given functions or move tests within modules.
Describe the solution you'd like
It would be great if Guida allowed testing private functions or modules in a clean and explicit way — for example, by having a mechanism (flag, annotation, or test-only import) to expose internal definitions during testing without making them publicly available in the actual package/app interface.
Describe alternatives you've considered
These are known in elm/test: expose functions I don't want to make part of the public API, give up on testing the given functions or move tests within modules.
Related Elm Features
Elm has no built-in way to test private functions afaik.
Is your feature request related to a problem? Please describe.
I'm often frustrated when I want to write tests for internal helper functions but can't access them due to module encapsulation. This forces me to either expose functions I don't want to make part of the public API, give up on testing the given functions or move tests within modules.
Describe the solution you'd like
It would be great if Guida allowed testing private functions or modules in a clean and explicit way — for example, by having a mechanism (flag, annotation, or test-only import) to expose internal definitions during testing without making them publicly available in the actual package/app interface.
Describe alternatives you've considered
These are known in
elm/test: expose functions I don't want to make part of the public API, give up on testing the given functions or move tests within modules.Related Elm Features
Elm has no built-in way to test private functions afaik.