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

Fix issue #781 #785

Merged
merged 1 commit into from
Sep 10, 2024
Merged

Fix issue #781 #785

merged 1 commit into from
Sep 10, 2024

Conversation

ArquintL
Copy link
Member

@ArquintL ArquintL commented Aug 27, 2024

Executing Paths.get(filename).getParent fails if filename is a relative path in the current folder (and thus does not have any path component besides the filename itself).

Please let me know if you have a great idea for a test case as we would need to invoke Gobra relative to a folder containing a Gobra file such that we can provide a path to the Gobra file without any path component.

Fixes #781

@ArquintL ArquintL requested a review from jcp19 August 27, 2024 06:40
Copy link
Contributor

@jcp19 jcp19 left a comment

Choose a reason for hiding this comment

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

LGTM! I guess the best way to have systematic tests for this would be to introduce UX tests after running Gobra's current test suit. For the former, we would first need to produce a gobra jar and then we would run it against a set of full Gobra commands provided by us

@ArquintL ArquintL merged commit bfdd55a into master Sep 10, 2024
3 checks passed
@ArquintL ArquintL deleted the issue-781 branch September 10, 2024 04:51
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.

NullPointerException for file-name-only paths
2 participants