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
Referencing TypeScript definition files #660
Comments
Can you link to the documentation where this If it's sufficiently common, I'm fine adding an exception for this. We already have a few exceptions for other tooling. |
Here is the TypeScript documentation for the |
@feross which exceptions do you refer to? iirc in hindsight the sentiment wasn't entirely favor of non-standard additions to standard (like JSX), even though it's been a huge drive in standard's adoption I feel that if this were to become a rule, it should be strict; e.g. only allow it for a leading comment on the first line - disabling comment validation in its entirety would probably be undesireable |
To add more to my opinion I want to use standard as it is a simple ruleset to adhere to but it's not usable if it hinders, and provides no alternative, to something that a developer sees as necessary. Regarding the format I just want something that works. 😄 |
@yoshuawuyts You can see the list of exceptions to the The point of
So, IMO, we should just allow it, especially if it's a directive used by popular tools. We already allow:
Note, a space is still required after the |
@feross fair point, ACK on this change |
Okay, adding this to the |
This will be part of standard v9. Since this relaxes a rule, there is no ecosystem impact. |
To use definition files for libraries to provide IntelliSense is increasing.
I'd like to be able to use this as acceptable by standard
/// <reference path="jquery/index.d.ts" />
Currently I get the
The text was updated successfully, but these errors were encountered: