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

mandatory/optional cannot be used as property names #1037

Closed
e-grigorov opened this issue Aug 14, 2018 · 0 comments
Closed

mandatory/optional cannot be used as property names #1037

e-grigorov opened this issue Aug 14, 2018 · 0 comments

Comments

@e-grigorov
Copy link
Contributor

Recently, we switched to M4 build and got some new fails in our TCs. The problematic scenario is a property with a name: "mandatory" or "optional" i.e.

functionblock Testable {
	status {
		mandatory optional as boolean with {
			eventable : true
		} <NULLABLE false>
	}
}

or

functionblock Testable {
	status {
		mandatory mandatory as boolean with {
			eventable : true
		} <NULLABLE false>
	}
}

org.eclipse.vorto.core.api.model.datatype.Property.getName() returns null but should return "optional" or "mandatory" as a name.

Ebolon added a commit to Ebolon/vorto that referenced this issue Aug 16, 2018
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

1 participant