Skip to content

Conversation

lwjohnst86
Copy link
Member

Description

Something has been bugging me for a while with our potential workflow, especially around the resources. One idea could be that we use main.py in the parent folder to coordinate all the tasks, and keep the scripts to hold the python functions that are used in main.py. Then we can simplify to write_properties(), read_properties() and no updating function. And we use the PackageProperties in main.py as the source of truth for the properties.

Then we can make templates to create a script of the extracted resource properties as functions.

This PR needs an in-depth review.

Copy link
Contributor

@martonvago martonvago left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally this makes sense to me. So, as you say, the object definition will be the source of truth, and it will basically be exported/backed up as datapackage.json.

import seedcase_sprout as sp


def resource_properties_seed_beetles():
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this need to be a function?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, I guess not. I didn't immediately think that variables can be called from other scripts.

@github-project-automation github-project-automation bot moved this from In Review to In Progress in Iteration planning May 28, 2025
Copy link
Member

@signekb signekb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this idea. This will simplify some things 👍 I agree with Marton's comments.

@lwjohnst86 lwjohnst86 moved this from In Progress to In Review in Iteration planning May 28, 2025
@lwjohnst86 lwjohnst86 requested review from signekb and martonvago May 28, 2025 11:33
Copy link
Contributor

@martonvago martonvago left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!! ⭐

@lwjohnst86 lwjohnst86 merged commit d9e9e66 into main May 28, 2025
1 check passed
@lwjohnst86 lwjohnst86 deleted the refactor/potential-way-of-coordinating-things branch May 28, 2025 13:33
@github-project-automation github-project-automation bot moved this from In Review to Done in Iteration planning May 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants