Skip to content

Incorrect XLSX parsing #1166

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

Open
AndrewKis opened this issue Apr 30, 2025 · 1 comment
Open

Incorrect XLSX parsing #1166

AndrewKis opened this issue Apr 30, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@AndrewKis
Copy link
Contributor

pjTDYzyiTmEte21D_oIlIY6HL8t_5FH7f-Global Library Data.xlsx

After read has incorrect type in several columns - doesn't recognize empty cells as nulls but as String:

Image Image
@AndrewKis AndrewKis added the bug Something isn't working label Apr 30, 2025
@Jolanrensen
Copy link
Collaborator

Jolanrensen commented Apr 30, 2025

null is better than empty string indeed. That way we can use fillNulls {}.
Maybe we could streamline it with dataframe-csv. It uses ParserOptions with nullStrings containing "", "null", "NA" etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy