Over the course of the last several weeks I have written two or three small CSV/XLS export modules and one moderately-sized CSV/XLS import module. I didn't use CSVelte for a number of reasons, the most obvious of which is that CSVelte hasn't reached API stability yet and I don't want to have to rewrite these modules in a week when I release the next version of CSVelte. But beyond that, as much as I hate to admit it, CSVelte isn't production-ready. I've been focusing on all the wrong things (I've been focusing on the areas I find interesting rather than the ones that are most useful). Anyway, for this next version I want to try to reprioritize. I want to try to focus as much as possible on only features that help the end-user work with CSV data. This means moving onto the Tabular data features. The schema features. The foreign key features. etc. etc. etc.
To get a better idea of what this library is missing and where its most egregious design flaws are, I think it would be best to actually write a CSV import/export module with it. One for Symfony, one for Laravel, and possibly one for ZF2 (we'll see). In addition to this I will likely write some basic boilerplate/framework integration code that I may even include with CSVelte in a lib or extras directory (rather than src).
Over the course of the last several weeks I have written two or three small CSV/XLS export modules and one moderately-sized CSV/XLS import module. I didn't use CSVelte for a number of reasons, the most obvious of which is that CSVelte hasn't reached API stability yet and I don't want to have to rewrite these modules in a week when I release the next version of CSVelte. But beyond that, as much as I hate to admit it, CSVelte isn't production-ready. I've been focusing on all the wrong things (I've been focusing on the areas I find interesting rather than the ones that are most useful). Anyway, for this next version I want to try to reprioritize. I want to try to focus as much as possible on only features that help the end-user work with CSV data. This means moving onto the Tabular data features. The schema features. The foreign key features. etc. etc. etc.
To get a better idea of what this library is missing and where its most egregious design flaws are, I think it would be best to actually write a CSV import/export module with it. One for Symfony, one for Laravel, and possibly one for ZF2 (we'll see). In addition to this I will likely write some basic boilerplate/framework integration code that I may even include with CSVelte in a
liborextrasdirectory (rather thansrc).