-
Notifications
You must be signed in to change notification settings - Fork 64
Crash when using non-empty input-renaming-map #124
Comments
Any reason this wasn't merged yet? The problem still exists, and @Yannic's commit fixes it. |
@elipoultorak it does fix it but if memory serves, it just disables the input renaming map? or did it work for you? if so then yeah why isn't this merged lol |
TBH, I don't remember what problem I was trying to solve when I initially run into this crash, and I haven't seen it for the last two years. |
I just tried it, and for some reason, it does rename it properly with the fix. I used a CLOSURE_COMPILED format instead of json, so I don't know if it would work with json. But when I use the master branch, or the last release, it gives me an error. When I use @Yannic's fork, it uses the correct renaming according to the map. |
Update: it also works with json maps. |
AFAIK, the crash above happens because the map isn't initialized at all. You're right that my fix works, but the map is only initialized right before the crash would happen and not where the initialization is supposed to happen. |
@elipoultorak @Yannic sick, ha ha |
i have a fork of |
Looks good, but is nobody at Google merging anything to this repo? |
@elipoultorak welcome to the gap between regular open source, and google internal :) lol |
Closure Stylesheets crashes with the following exception when using an non-empty input-renaming-map. The format of the renaming map does not seem to matter, it only must not be empty.
Repo:
java -jar closure-stylesheets-1.5.0-SNAPSHOT-jar-with-dependencies.jar --input-renaming-map renaming.json some.css
renaming.json
some.css
Content does not matter, can be empty.
The text was updated successfully, but these errors were encountered: