You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All package contents are not accessible through the package due to the name of the main class. For example, the class MungoError can still be accessed as long as no package name is defined; Accessing the class with package name MungoHealer.MungoError is always failed.
The text was updated successfully, but these errors were encountered:
@Dschee For a certain entity, we can just import it directly with swift default import declaration like
import protocol MungoHealer.BaseError
But in some cases, e.g. adding a new custom ErrorHandler, there is some efforts behind. A ton of related entities like BaseError, ... is required and has to be imported one-by-one.
For a long term solution, I prefer to rename the main class MungoHealer to Healer or something else that does not duplicate the package name. What do you think?
If that fixes the issue, I'm not against renaming MungoHealer (though I feel it's weird that we need to do this). I'd prefer Mungo over Healer though, since in the example code we also just name the global variable mungo – the type would fit then. Would you like to create a PR (and test if that actually solved the problem)?
All package contents are not accessible through the package due to the name of the main class. For example, the class
MungoError
can still be accessed as long as no package name is defined; Accessing the class with package nameMungoHealer.MungoError
is always failed.The text was updated successfully, but these errors were encountered: