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

Feature/cash bleeders #30

Merged
merged 18 commits into from
Jun 17, 2024
Merged

Feature/cash bleeders #30

merged 18 commits into from
Jun 17, 2024

Conversation

gbsDojo
Copy link
Collaborator

@gbsDojo gbsDojo commented Jun 14, 2024

Adding Utils methods;

Adding Pytest for Utils methods;

Testing Pytest workflow with github actions behavior for Pull Requests;

@gbsDojo gbsDojo requested a review from tacio June 14, 2024 20:52
tacio
tacio previously approved these changes Jun 14, 2024
Copy link
Contributor

@tacio tacio left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@tacio tacio left a comment

Choose a reason for hiding this comment

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

Left some comments, but just some food for thought for future improvements.

- name: Install dependencies
run: |
python -m pip install --upgrade pip
pip install --upgrade --upgrade-strategy eager -r .github/workflows/utils_requirements.txt
Copy link
Contributor

Choose a reason for hiding this comment

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

Why always upgrade pytest instead of fixing its version?

pip install --upgrade --upgrade-strategy eager -r .github/workflows/utils_requirements.txt
- name: Run tests
run: |
pytest --junitxml=report.xml
Copy link
Contributor

Choose a reason for hiding this comment

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

Is the report retrievable later?

Copy link
Contributor

Choose a reason for hiding this comment

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

Just for the record... Why all the changes in the requirements?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It turned out that these bibs were unnecessary

if not isinstance(name, str) or not isinstance(data_type, str):
raise ValueError("Each tuple must contain a column name and data type as strings.")
if data_type.upper() not in valid_types:
raise ValueError(f"Invalid data type '{data_type}'. Supported types are: {', '.join(sorted(valid_types))}")
Copy link
Contributor

Choose a reason for hiding this comment

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

inform which column had the invalid data_type

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Good one, This should go for a improvements section

@gbsDojo gbsDojo merged commit 319eec9 into main Jun 17, 2024
3 checks passed
@gbsDojo gbsDojo deleted the feature/cash_bleeders branch June 17, 2024 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants