Skip to content

File.LinkError - fix confusing wording #14441

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

Conversation

demerphq
Copy link
Contributor

The api for links is ln(existing, new) but the old text said "from existing to new", where it should have said "to existing from new".

This fixes the text to make it more clear. Likely this error came from the example using "source.txt" and "target.txt" and it being natural to say "to target".

This changes the example to use "existing.txt" and "link.txt" so it is more obvious what is going on.

@demerphq demerphq force-pushed the yves/make_file_link_error_text_less_confusing branch from 6e7cdbb to f115784 Compare April 16, 2025 14:18
The api for creating links is ln(existing, new) but the old error text
said "from existing to new", where I believe it should say "from new to
existing".

Likely this error came from the example using "source.txt" and
"target.txt" and it being natural to say "to target", so this patch also
changes the example to use "existing.txt" and "link.txt" as the file
names so it reads more naturally.
@demerphq demerphq force-pushed the yves/make_file_link_error_text_less_confusing branch from f115784 to eac3b53 Compare April 16, 2025 16:17
@josevalim josevalim merged commit 82ccb94 into elixir-lang:main Apr 17, 2025
11 checks passed
@josevalim
Copy link
Member

💚 💙 💜 💛 ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants