We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be good to decide on our convention on how we import packages and the short hands for them. (e.g. CA for ClimaAtmos).
import PackageName as PN
import PackageName
import ClimaCoupler.Module: struct1, function1, function2, ...
The text was updated successfully, but these errors were encountered:
juliasloan25
Successfully merging a pull request may close this issue.
It would be good to decide on our convention on how we import packages and the short hands for them. (e.g. CA for ClimaAtmos).
solution
import PackageName as PN
(e.g. ClimaAtmos -> CA, SurfaceFluxes -> SF)import PackageName
(e.g. for Dates or JLD2)import ClimaCoupler.Module: struct1, function1, function2, ...
package shorthands:
The text was updated successfully, but these errors were encountered: