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

Improve documentation about encoding option #793

Conversation

Jhonatannunessilva
Copy link
Contributor

This PR resolves #791

After this PR:

DataFrame.from_csv/2:

image

DataFrame.load_csv/2:

image

@@ -627,6 +630,7 @@ defmodule Explorer.DataFrame do
* `:eol_delimiter` - A single character used to represent new lines. (default: `"\n"`)
* `:backend` - The Explorer backend to use. Defaults to the value returned by `Explorer.Backend.get/0`.
* `:lazy` - force the results into the lazy version of the current backend.
* `:encoding` - Encoding to use when reading the file. For now, the only possible values are `utf8` and `utf8-lossy`. The utf8-lossy option means that invalid utf8 values are replaced with � characters. (default: `"utf8"`)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@philss Should we make them atoms instead of regular strings?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@josevalim yeah, I think so!

@Jhonatannunessilva there is an example of what we want to do in #770
But if you prefer, we can do in another PR as well :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No problem, I can do it in this PR

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we talked privately, this is going to be changed in another PR :)

@philss philss merged commit 2ecf0ff into elixir-explorer:main Jan 19, 2024
3 checks passed
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

Successfully merging this pull request may close these issues.

Question/Possible improvement about the encoding option in the DataFrame.from_csv/2 function
3 participants