-
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
Allow opt-out of global Xrm namespace #181
Comments
Given that half of the files are static, my gut tells me the right approach is to:
Then:
This will leave everything working backwards compatible, while adding a new command line and configuration option to specify the custom namespace(s). This would also open up the door for more customization of other things down the road, via tokenization. E.g:
|
I love the idea! You should definitely submit a PR |
I wrote a tool to do this for me post generation. It also does other additional tapings for some custom libraries, but I'm not ready to share it as of yet (although it's on my github profile, so if you're really crazy, you can look at it if you want) |
We have this same issue, a collision between XRMDT and @types/xrm. Just allowing a parameter to set the generated namespace to something other than Xrm seems simple and should fix the problem. Or did DlaB ever publish his post-op tool? @daryllabar any hints? |
Hi @daryllabar , guess you meant "xdt-formext"? Have you lately been able to successfully use jest with xdt but without using your tool? Afaik your npm package "xdt-formext" isn't available anymore and I struggled to implement everything according to TypeScripting the Heck Out Of Model Driven Forms.
Hi @majblackburn too, do you have any news on this issue? I don't want to use @types/xrm at all. |
I've haven't tried XDT without my post processor. My name package is still available: |
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
We're looking to unit test our webresources using
xrm-mock
, as it's the only mature type-safe testing library for the Xrm Api.However,
xrm-mock
is typed against@types/xrm
and therefore cannot be used in conjunction with XDT.Describe the solution you'd like
A clear and concise description of what you want to happen.
E.g:
Would become:
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I have tried a thousand things other the sun, but there is no alternative. Typescript attempts to merge declared namespaces found in declaration files, and there is no way to opt out.
This means right now you use XrmDefinitelyTyped, or any other libraries typed against
@types/xrm
.Additional context
Add any other context or screenshots about the feature request here.
I would be happy to submit a PR to do this.
The text was updated successfully, but these errors were encountered: