Replies: 2 comments
-
I like it; you need to do the same for |
Beta Was this translation helpful? Give feedback.
0 replies
-
Pull request has been submitted. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Wondering why the the typing for getAttribute are all cast to Attributes.Attribute
Changing to the more specific Xrm typing (ex
Xrm.Attributes.LookupAttribute
) would save having to lookup what these types are and having to cast things after getting the value.Also if the type definition was refreshed and a data type changed or the field was removed it would also allow for the project to start throwing some errors in the IDE when these values are being sent to methods that no longer support there type.
I made a fork and made the following changed and it works great.
In the createAttributeMethod can change
dom.create.alias(xrmAttribute, dom.type.undefined, dom.DeclarationFlags.None)
to
dom.create.namedTypeReference(AttributeTypeDefinitions.get(attr.AttributeType)??"Xrm.Attributes.Attribute")
Pulling from new mapping for attribute types in constants file
I feel falling back to
Xrm.Attributes.Attribute
is probably best for the more obscure types.Beta Was this translation helpful? Give feedback.
All reactions