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

commoner's grep for @providesModule turns up vim swap files #111

Closed
sophiebits opened this issue Jun 19, 2013 · 6 comments
Closed

commoner's grep for @providesModule turns up vim swap files #111

sophiebits opened this issue Jun 19, 2013 · 6 comments
Assignees

Comments

@sophiebits
Copy link
Collaborator

I was getting errors from grunt because of this and maybe this was also causing some confusion of mine before. Not sure what the right thing to do here, but perhaps it should filter by file extension (and hidden-ness? my vim swap filenames start with ..)

@zpao
Copy link
Member

zpao commented Jun 26, 2013

@benjamn Should we fix this in commoner?

@benjamn
Copy link
Contributor

benjamn commented Jul 1, 2013

Oh, interesting. I dealt with a related problem with Emacs ~ files a while back:
benjamn/commoner@4ed07b3

Definitely a thing that Commoner should handle intelligently.

@ghost ghost assigned benjamn Jul 1, 2013
@benjamn
Copy link
Contributor

benjamn commented Jul 1, 2013

What if the tie was broken according to the length of the filename (shortest wins)? Is that too much of a hack?

@zpao
Copy link
Member

zpao commented Jul 1, 2013

What do other things (like coffee) do? This can't be a new problem...

@benjamn
Copy link
Contributor

benjamn commented Jul 2, 2013

@zpao good call; turns out CoffeeScript doesn't try to be super clever about this: https://github.com/jashkenas/coffee-script/blob/8e90aaefc1/lib/coffee-script/command.js#L33-L35

@benjamn
Copy link
Contributor

benjamn commented Jul 2, 2013

Fixed in Commoner 0.8.1: https://github.com/benjamn/commoner/issues/31

@benjamn benjamn closed this as completed Jul 2, 2013
taneliang referenced this issue in MLH-Fellowship/react Aug 17, 2020
Summary
---

Resolves #44.

Intended to highlight all related React events. However, it looks like
separate promises can have the same wakeable ID, which is a bit strange.

TODO
---

* Ensure that we are correctly understanding wakeable IDs, i.e. that
  a unique resource/promise is a unique wakeable.
* Check if `unstable_createResource` caches promises.

Test Plan
---

* `yarn lint`
* `yarn flow`: no errors in changed code
taneliang referenced this issue in MLH-Fellowship/react Aug 19, 2020
Summary
---

Resolves #44.

Intended to highlight all related React events. However, it looks like
separate promises can have the same wakeable ID, which is a bit strange.

TODO
---

* Ensure that we are correctly understanding wakeable IDs, i.e. that
  a unique resource/promise is a unique wakeable.
* Check if `unstable_createResource` caches promises.

Test Plan
---

* `yarn lint`
* `yarn flow`: no errors in changed code
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

No branches or pull requests

3 participants