Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing NuGet Package #7

Open
RomainDGx opened this issue Feb 2, 2024 · 2 comments
Open

Missing NuGet Package #7

RomainDGx opened this issue Feb 2, 2024 · 2 comments

Comments

@RomainDGx
Copy link

I am interested in incorporating your projects as dependencies in my application. However, I am unable to locate any corresponding packages on nuget.org. Have you already published packages for these projects, or is there a plan to do so after implementing the writing API?

For my specific use case, I require functionality to read and parse CSV files, and the current state of the project adequately meets my requirements.

Do you have any plans to publish your project on nuget.org? If so, would you appreciate assistance in this regard?

Thank you for your efforts.

@olivier-spinelli
Copy link

(Disclaimer: I'm Romain's colleague)

I just want to add that I'd love to have a split between read and write functionnalities:

  • FlameCsv.Core with the common types.
  • FlameCsv.Reader and FlameCsv.Writer

I understand that this dichotomy would have to be propagated to FlameCsv.SourceGen but nevertheless, I'd love it!

And I also wanted to add thank you very much for your very very good code!

@ovska
Copy link
Owner

ovska commented Feb 5, 2024

Thanks for your interest! The writing code is still missing the final API shape, which is why the code hasn't been released yet.

As for splitting the writing and reading code, it is possible but since I eventually settled on S.T.Json style "Converter"-style shape (instead of separate Parsers and Formatters), the split would not be all that clean and a lion's share of the code would still reside in Core.

While the reading API is completely functional, I will try to find time to finish the writing API too so I could in good conscience release a package. Help is of course appreciated from that point on, both in the specifics of releasing a package, and possible improvements to the library.

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

No branches or pull requests

3 participants