Ernesto García
Ernesto García
I'll look into it.
This was how the library behaved initially, but I received the opposite complaint, and frankly I think that keeping a fatal error silent, only to be handled by the `:import_failed`,...
So instead of an exception, you propose to give back the info to the caller via a return value, isn't it? What do you suggest this return value should be,...
I think is nice. I would only ask for it to be configurable (i.e. the user can opt into this behavior) and that it is accompanied by some corresponding tests.
Yup, the same with me. I wish I had more time to devote to this project :( But let me know if you need any help.
No there is not. There is a way to define an importer to act on a specific sheet, which you can reference by name. What if you create an importer...
I think you could maybe create importers dynamically in runtime. Ruby is dynamic and flexible enough to allow this. But maybe you'll need some meta programming. As to wether give...
I'll make a PR for this
I still think that in cases like this particular one, there's nothing wrong with the `if/else` clause with both code branches in it. I don't see why it should be...
I agree with you, but how does that reasoning makes this: ``` ruby def some_method(thing) if thing[:foo][:bar] partial_compute(thing) else re_compute(thing) end end ``` less acceptable than this: ``` ruby def...