CSV plugin; New TypeScript example; Usability improvements.
The main reason it's a separate plugin is because it brings in a medium sized JavaScript library for handling CSV. If it was built in to the Array object, it would bloat every project using Array with a CSV library, even if the project doesn't use CSV at all. So it helps keep projects lightweight.
The CSV plugin should be doing exactly the same thing as it would if it was built in to the Array object. What limitations does it have?
There is also a small suggestion. I think this icon will be more beautiful if you use 'CSV' instead of the comma icon.( Search 'csv file icon' on google)
There may be a misunderstanding in the words I expressed. In fact, what I want to say is that the function of the CSV plug-in is relatively simple, and it is a bit wasteful to use it as a plug-in alone.
If it were a separate plugin, I always wonder why it couldn't do more. But if it is one of the actions in the Array plugin, I will think, oh, it turns out that he can still do this!
Because third-party CSV plugin have richer functions, they have a good debugger panel. and allows operations on CSV, and some simple data search actions, identifying the first row/column as the title, search and indexing rows/columns.it is to implement basic Excel formulas basically.
Although the existing functions can also be achieved through other methods of Construct, some additional steps and detours are required.But the purpose of using plug-ins is to reduce workload.
This is definitely not a complaint, I'm super excited to finally have a built-in CSV plugin! thank you for all your work!