-
-
Notifications
You must be signed in to change notification settings - Fork 762
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
Made typings plugin friendly & add typings for every package #770
Made typings plugin friendly & add typings for every package #770
Conversation
@crutchcorn please rebase so the CI runs |
This central typing may likely be incorrect and need further revisions I am making so many commits to ensure I (and others) can track my progress as I figure out the type system for jimp
@hipstersmoothie done |
Wanted to check on the status of this. Seems that tests have passed |
@crutchcorn sorry! I'm the only maintainer on this and really don't use jimp at all in my work. So I'm a little slow at getting to the issues. I haven't had time to take a proper look at this, but I'll look at it tomorrow |
No worrier in the slightest. I know how maintaining something like this that we don't use ourselves goes. Just wanted to give a small bump cuz I know I need reminders on the one I maintain 😁 |
Really liking what I'm seeing though. I'd prefer to make the change as breakingless as possible. Would that be easy? |
Actually, if I did this properly this is not a breaking change in terms of the main Jimp typings. If you'd like, I can export the same other typings (ala the font options, etc) and then it will be 100% non-breaking change Would be an extremely trivial task, could take care of it tonight |
Yeah do that and I think this is good to merge
…On Sat, Aug 31, 2019 at 9:39 PM Corbin Crutchley ***@***.***> wrote:
Actually, if I did this properly this is not a breaking change in terms of
the main Jimp typings. If you'd like, I can export the same other typings
(ala the font options, etc) and then it will be 100% non-breaking change
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#770>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJDEBCGXOJJS7V4I3AWEQ3QHNBRVANCNFSM4IJ3DVZQ>
.
|
Actually, you know what? I was just about to make that "fix", but then realized that none of the other types in that file were actually exported as of the current-most up-to-date version of said file (per commit 466b65b), so this PR in it's current state is already not a breaking change. |
how can i convert .jpg to .png temporarily? |
Mmm, apologies. I'm going to reject my own PR until I can fix some issues with it. I'll try to have them fixed in the next day or two. Huge apologies for bumping when things aren't fully working >~< |
Move typing files to proper locations, included typing file in package.json files, fix the configure function typings
So sorry once again for bumping before being ready. I have now double and tripple checked that this should work in my own project which uses the |
Actually, while this can totally be a patch for |
# Conflicts: # packages/jimp/jimp.d.ts
Merge conflicts resolved, Still not a breaking change :) |
🚀 PR was released in v0.8.0 🚀 |
What's Changing and Why
Previously, there was a single index.d.ts file in
jimp
. However, if you wanted to use any of the@jimp
files, you were unable to get the typings for them individually.This meant a few things:
@jimp/custom
The second point was made even clearer as this went on as there were a few plugins that had no type information previously (thusly making the
jimp
package type info incomplete). As a result, the following plugins now have typings on thejimp
package that were previously not present:What else might be affected
This will likely be a breaking change for
jimp
(unless we want to export the same typings as before usingexport * from '@jimp/core
or something similar)Tasks
jimp.d.ts
Published PR with canary version:
0.7.1-canary.770.193.0