-
Notifications
You must be signed in to change notification settings - Fork 0
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/reapply fixes #5
Conversation
d95a527
to
646b6be
Compare
.appendingPathComponent("\(testName).\(identifier)") | ||
.appendingPathExtension(snapshotting.pathExtension ?? "") | ||
|
||
// Check the bundle for the resource first, then the file system |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you clean up the indenting of the code?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you done a local build of the puffin repo using this proposed commit? If it doesn't pass for you locally, I'm not sure if it will pass on CI, so it would be good to check. If it doesn't pass, we may still not be able to upgrade this library yet.
// But, if we're recording, don't bother checking the bundle, since we aren't comparing it to anything, and | ||
// want the new file to be generated in the source directory, not the bundle. | ||
var snapshotFileUrlCandidate: URL? | ||
if record != .never { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't we want to check the bundle if the recording is never
or missing
? Because we'd need to know if the snapshot existed before deciding whether to record... So, this comparison seems incorrect - should it be record != .always
? Then, if the file isn't found in the bundle, create it in the snapshot directory.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, good call. Will change.
Testing this locally before I call it good for another look. |
Alright, I did run the puffin repo against this branch, and things are working as I expect them to, so I think this is good to go. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
No description provided.