Skip to content

Conversation

flovan
Copy link

@flovan flovan commented Dec 8, 2015

Rather than using the getFilepath'd filename to get the extension, I use the original path and pass the extension directly into the transform constructor.

Florian added 3 commits December 8, 2015 10:23
Rather than using the `getFilepath`'d filename, get the extensions of the original path, and pass it into the transform constructor.
@flovan
Copy link
Author

flovan commented Dec 8, 2015

Oops my bad, it seems my changes would be breaking to the api, making this more of a 4.0.0. I'll have to rethink how to handle this situation. Suggestions are welcome of course!

Copy link

Choose a reason for hiding this comment

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

Don’t bump package version. This is module owners job.

@joakimbeng
Copy link
Member

For me a breaking change is not a big deal, I'm working on another small breaking change anyway.
But this change makes the transform function's argument list too long to be useful IMO.
Maybe a better and future proof transform function API would be to just have two arguments: filepath and options. Where options is an object which contains all other params. What do you think?

@joakimbeng joakimbeng mentioned this pull request Mar 17, 2016
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.

3 participants