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.

Sign up for GitHub

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

Jump to bottom

esgmigrate and esgpublish disagree on field name (project_cfg vs user_project_config) #249

Open
pchengi opened this issue Feb 6, 2025 · 1 comment
Open

esgmigrate and esgpublish disagree on field name (project_cfg vs user_project_config) #249

pchengi opened this issue Feb 6, 2025 · 1 comment

Comments

@pchengi
Copy link

pchengi commented Feb 6, 2025

Version of esgpublish: v5.2.4

When esgmigrate is used to convert a project's ini file, it generates a yaml file with a field project_cfg. When this file is then parsed by esgpublish, it prints a warning same project config could not be parsed.
When the field is renamed to user_project_config, the warning disappears.
@sashakames
Copy link
Contributor

Great catch thanks @pchengi !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pchengi @sashakames