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

issues/133 (part 1): Make predictions based on Class instance instead of class name #190

Merged
merged 1 commit into from
Nov 12, 2024

Conversation

fmck3516
Copy link
Member

@fmck3516 fmck3516 commented Nov 12, 2024

This provides a richer context for Skippy to make skip-or-execute decisions (e.g., the location of the class file).

The purpose of this PR is to ship the overall work for #133 in smaller increments. This PR itself does not resolve #133

@fmck3516 fmck3516 self-assigned this Nov 12, 2024
@fmck3516 fmck3516 changed the title issues/162: part 1 - make predictions based on Class instance instead of name issues/162: part 1 - make predictions based on Class instance instead of class name Nov 12, 2024
@fmck3516 fmck3516 changed the title issues/162: part 1 - make predictions based on Class instance instead of class name issues/133 (part 1): Make predictions based on Class instance instead of class name Nov 12, 2024
@fmck3516 fmck3516 merged commit 4dc6489 into main Nov 12, 2024
1 check passed
@fmck3516 fmck3516 deleted the issues/133-part-1 branch November 12, 2024 03:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for duplicate class names across output directories
1 participant