-
Notifications
You must be signed in to change notification settings - Fork 10
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
lowercase package name #7
Comments
OK, I see that you ended up copying this code to blackfriday (russross/blackfriday@8cc535d) to resolve russross/blackfriday#350. This was done in 2018 but no release since that time :( life is pain :-\ Closing this one |
Hi @kolyshkin, thanks for reporting this issue. There seem to be a few different things here.
This isn't true. Uppercase letters in import paths and package names are supported by Go. The tests for this package are passing, and it has been used by various other projects for years without issues. The issue you linked is very old and not related.
If you're seeing that behavior with the latest version of
A new v2 release that includes that change should indeed be made. Can you file an issue about it in the blackfriday issue tracker? |
I sort of hinted about it in russross/blackfriday#586 yesterday. |
Created: russross/blackfriday#587 To the readers of this: I found it's |
Apparently (golang/go#26456) golang doesn't like Uppercased letters in package names.
When I'm trying to use
gopls
in a repository (https://github.com/opencontainers/runc) that uses a package (github.com/russross/blackfriday/v2
) that uses this package (i.e.github.com/shurcooL/ sanitized_anchor_name
), I end up with the following error:I look into go package cache, and here it is:
I realize my request might look idiotic, but can you please consider renaming your repo to be all lowercase, or move this package under some other path that would all be lowercase?
The text was updated successfully, but these errors were encountered: