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.

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

[GSProcessing] Supplement for GConstruct Config Check for GSProcessing #937

Merged

Conversation

jalencato
Copy link
Collaborator

@jalencato jalencato commented Jul 26, 2024

Issue #, if available:
#747

Description of changes:

  • We do not need to build another GConstruct Config Validator because most of the functions have already been included in our GConstruct Config Converter. It suffices if we just fix for some corner cases.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@jalencato jalencato added the ready able to trigger the CI label Jul 26, 2024
@jalencato jalencato marked this pull request as ready for review July 29, 2024 20:36
@jalencato jalencato force-pushed the gconstruct_gsprocessing_config_validation branch from 0e817a3 to b217b4b Compare July 30, 2024 22:09
@jalencato jalencato requested a review from thvasilo July 30, 2024 22:15
@thvasilo
Copy link
Contributor

Code looks good, could we add 1-2 tests that ensure the assertions are raised for invalid input? Use https://docs.pytest.org/en/7.1.x/how-to/assert.html#assertions-about-expected-exceptions

@jalencato jalencato linked an issue Aug 1, 2024 that may be closed by this pull request
@jalencato jalencato merged commit a9ea274 into awslabs:main Aug 1, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready able to trigger the CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[GSProcessing] GConstruct config input checker for GSProcessing
2 participants