Skip to content

Conversation

@StephanieKemna
Copy link
Collaborator

Resolves #52

One way to test this, is to use this branch and run pytest, and then check against having the old code in read_files.py (see commit changes).

Another way to test is to use the main branch and this branch, and try the same command for reading the situation and target ship files from somewhere else on the system, and it will bomb on main (see issue description).

@StephanieKemna StephanieKemna added the bug Something isn't working label Apr 3, 2025
@StephanieKemna StephanieKemna self-assigned this Apr 3, 2025
@StephanieKemna StephanieKemna linked an issue Apr 3, 2025 that may be closed by this pull request
Copy link
Collaborator

@tomarnepedersen tomarnepedersen left a comment

Choose a reason for hiding this comment

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

Checked and working

@tomarnepedersen tomarnepedersen changed the base branch from main to dev April 24, 2025 06:44
@tomarnepedersen tomarnepedersen merged commit a4ca806 into dev Apr 24, 2025
8 checks passed
@tomarnepedersen tomarnepedersen deleted the 52-issue-reading-commandline-input-data branch April 24, 2025 06:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Issue reading commandline input data

2 participants