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

Add support for custom TypeMapping #2991

Closed
smitpatel opened this issue Sep 2, 2015 · 2 comments
Closed

Add support for custom TypeMapping #2991

smitpatel opened this issue Sep 2, 2015 · 2 comments

Comments

@smitpatel
Copy link
Contributor

At present we are making changes to our property discovery so that all the types supported by the provider can be mapped as primitive properties. In the addition to provider supported types, user may want to use some other type as a primitive by providing a custom typemapping through which it can be mapped to one of the known types of the provider and subsequently be used as a primitive property.
Also see #2588

@divega
Copy link
Contributor

divega commented Sep 3, 2015

@smitpatel this might be a dupe of #242. Although I like the title and the details you put into this bug, we have referred to the other bug a few times. I don't care too much about which one wins 😄

@smitpatel
Copy link
Contributor Author

I have updated the other issue and closing this.

@divega divega removed this from the Backlog milestone May 8, 2017
@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
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