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

Operation name cannot be same as custom type (Enum / Entity) name #965

Closed
e-grigorov opened this issue Jun 15, 2018 · 1 comment
Closed

Comments

@e-grigorov
Copy link
Contributor

I got this error message with this model:

using com.mycompany.type.Record ; 1.0.0

functionblock Recorder {
	operations {
		mandatory record() returns Record
	}
}

It's somehow strange limitation. What is the reason to have this restriction?

@Ebolon
Copy link
Contributor

Ebolon commented Jun 15, 2018

I think you mean this error: "Operation name cannot be same as custom type (Enum / Entity) name". Yes this is strange. Would suggest to remove the validation check checkOpNameAgainstEntityName. @aedelmann ?

Ebolon added a commit to Ebolon/vorto that referenced this issue Jun 15, 2018
…for datatype property recursion and same name validation for function block operation name

Signed-off-by: Simon Pizonka <[email protected]>
Ebolon added a commit to Ebolon/vorto that referenced this issue Jun 21, 2018
… not have the same name as an entity.

Signed-off-by: Simon Pizonka <[email protected]>
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

2 participants