-
Notifications
You must be signed in to change notification settings - Fork 487
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose the "formatPatch" function #399
Comments
Done! #451 |
Thank you! |
Any chance this can make it to npm, too? 鉂わ笍 |
Will do in the next few days, @martolini! |
It's unfortunate that @type/diff doesn't expose this yet :| |
@leonardobsjr I'm hoping to do #303 soon and have jsdiff take over its own type definitions instead of deferring the provision of them to DefinitelyTyped. I have absolutely no idea how to do this yet - first time! - so any help would be welcome. But if I succeed then the |
@ExplodingCabbage Did a super-barebones types inclusion: #496 |
Hi! 馃憢
Firstly, thanks for your work on this project! 馃檪
Today I used patch-package to patch
diff@5.1.0
for the project I'm working on.I'd like to use the provided
formatPatch
function along withstructuredPatch
, so that to only display a diff if relevant to my application (cannot apply the conditions on a string representation of the diff, sounds pretty hacky and fragile!).I think that
formatPatch
should hence be exported, to be used together withstructuredPatch
as I see fit, instead of directly viacreateTwoFilesPatch
that simply combines (and is very suitable anyway!)Here is the diff that solved my problem:
This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered: