-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
Rename the folder something else than # #30
Comments
@vjeux I've checked mercurial (on default configuration) and it sees folder without issues:
Still, I agree that some may rely on .hgignore (or .gitignore) which will hide those folders from them. I'm not sure what better alternative to |
You are right, we had an ignore rule for emacs autosave files that start with In any case, while it's fun to use esoteric characters, in practice it is prone to cause issues like this. This is especially annoying since this is a dependency of a dependency of a dependency and not even the main purpose. I think that as your project gets more popular, this is likely going to cause more issues and would be nice to use traditional characters for filenames to avoid very annoying issues like this. |
@vjeux one alternative I see, is to rename |
Hey! I just found your project in the most unenjoyable way - when a build script totally broke down in the bowels of some other library! Please please please please do not use esoteric characters in file paths - while every filesystem can handle it, many tools can't. |
@DavidSouther Have you reported a bug to tools you used, that can't handle '#' in filename? it's certainly a serious bug, that should be reported :) |
There are a multiplicity of reasons tools might not handle esoteric paths, and yes, they should be improved to handle those cases. You have the ability to make it easier for other people to use your package; if you choose not to, that is your decision. |
@DavidSouther it's long time it's that way. I never had problems with it, and it's just two users that reported this issue to me so far. Additionally, I think it's really bad, that you come here with bug report, asking for an improvement, instead of reporting an obvious bug to issue tracker of tool that's broken. Sorry, but that's totally not convincing to me. |
Por que no los dos? (Why not both?) I unfortunately can't show you the bug report, as it's with an internal tool. I see you are not interested in this change; if the bug report were marked "Closed" I'd have immediately recognized that and not bothered you. |
@DavidSouther what would be changed is is that e.g. |
I believe I just ran into this using Google App Engine's Managed VMs, since Google Cloud Storage does not allow EDIT: seems like GAE is having issues with something other than the |
@silenceisgolden At this point plan is to merge constructor name with Concerning Google App Engine, questions is what utility is responsible for CJS modules resolution, as it's were problem occurs. Does Google App Engine does that on its own? |
@medikoo I think there is just a name validation check run on the files before they are uploaded to Google Cloud Storage, which from the there the code is run in the App Engine containers. See comment, it seems like they might be treating this as a bug so I'll see what their response is before continuing any patching http://stackoverflow.com/questions/33858024/app-engine-deploy-fails-managed-vm-nodejs?noredirect=1#comment55490045_33858024 |
@silenceisgolden great thanks for clarifying that! |
@medikoo according to http://stackoverflow.com/questions/33858024/app-engine-deploy-fails-managed-vm-nodejs?noredirect=1#comment55524984_33858024, GAE should allow for any name, so I'll pull out of this issue. For those who still feel strongly about this or find it later, the list of @medikoo libs that have deep references into
That does not count anything outside of @medikoo libs and in userland already, although hopefully everyone just does |
It's included in eslint which is fairly popular :) eslint@1.3.1 > escope@3.2.0 > es6-map@0.1.1 > es5-ext@0.10.7 |
@vjeux To clarify, yes I'm sure it is many more libraries, but the worry is due to the library design of deep linking to portions of the library such as |
Makes sense. That's a tough one :( |
Proposal for now: use trailing |
@medikoo using |
Unfortunately the There is a workaround, which is to basically replace the I have just implemented this fix for StackBlitz in order to resolve stackblitz/core#1390 |
@markwhitfeld this package is now rebranded as ext which doesn't use However |
Oh awesome. Thanks for your reply! |
Hey,
The fact that the folder had '#' in its name caused issues with mercurial as by default it considers it to be a temporary file. I was wondering if you would mind renaming it something else as while this is totally valid, it's going to subtly break many places.
Thanks!
The text was updated successfully, but these errors were encountered: