-
Notifications
You must be signed in to change notification settings - Fork 53
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
Split xrm.d.ts into a separate package #63
Comments
Any news about this enhancement? |
There is a problem with directly using the typings from @types/xrm with XrmDefinitelyTyped. The problem is that XrmDefinitelyTyped does not wish to allow magic strings in |
There is a PR submitted this week ((#278)) which allows XrmDT to use a custom namespace (instead of 'Xrm'). While I think the issue here may have other benefits, using a custom namespace avoids the collision between this project and @types/xrm, which I think was a prime motivator for this issue. |
It seems this issue has been going on for so long that another project has been created that is pure npm and combines types/xrm with XDT :) |
Max Ewing has made a blogpost, where he describes a use case for writing typescript that only interfaces with
xrm.d.ts
. Currently this is done by extracting the generated file and distribute it in some way.Although this is not the intended way of using XDT, I believe we should support it.
xrm.d.ts
is already used separately from the rest of XDT. Therefore it is possible to extract it into a new project and generate a separate package, preferably for each version of the file. This would allow Max Ewing to reference those packages, instead of having to generate it himself.The text was updated successfully, but these errors were encountered: