Skip to content

DATAMONGO-1053 - Only type check explicit language properties. #228

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

Closed
wants to merge 2 commits into from

Conversation

christophstrobl
Copy link
Member

We now only perform a type check only on via @Language explicitly defined language properties. Prior to this change non String properties named language cause errors on entity validation.

We now only perform a type check on via @language explicitly defined language properties. Prior to this change non String properties named ‘language’ cause errors on entity validation.
christophstrobl added a commit that referenced this pull request Oct 10, 2014
…e properties.

We now only perform a type check on via @language explicitly defined language properties. Prior to this change non-String properties named language caused errors on entity validation.

Original pull request: #228.
christophstrobl added a commit that referenced this pull request Oct 10, 2014
…e properties.

We now only perform a type check on via @language explicitly defined language properties. Prior to this change non-String properties named language caused errors on entity validation.

Original pull request: #228.
@odrotbohm odrotbohm closed this Oct 10, 2014
@odrotbohm odrotbohm deleted the issue/DATAMONGO-1053 branch October 10, 2014 09:32
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

Successfully merging this pull request may close these issues.

2 participants