|
Re: Customization of NamesAreUniqueValidator [message #1219595 is a reply to message #1219389] |
Wed, 04 December 2013 19:51 |
|
HI,
you could try todo something like
package org.xtext.example.mydsl.validation;
import org.eclipse.emf.ecore.EClass;
import org.eclipse.xtext.validation.NamesAreUniqueValidationHelper;
import org.xtext.example.mydsl.myDsl.MyDslPackage;
public class MyDslNamesAreUniqueValidationHelper extends
NamesAreUniqueValidationHelper {
@Override
protected EClass getAssociatedClusterType(EClass eClass) {
if (MyDslPackage.Literals.GREETING == eClass) return null;
return super.getAssociatedClusterType(eClass);
}
}
or change the nameprovider
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de
|
|
|
|
|
|
|
Re: Customization of NamesAreUniqueValidator [message #1383996 is a reply to message #1383948] |
Tue, 27 May 2014 18:18 |
|
Hi,
make sure that u you the validator at all
your impl looks very strange for me the following works fine for me
Model:
elements+=Element*;
Element:
AElement | BElement;
AElement:
"a" name=ID
;
BElement:
"b" name=ID
;
public class MyDslNamesAreUniqueValidationHelper extends
NamesAreUniqueValidationHelper {
@Override
protected EClass getAssociatedClusterType(EClass eClass) {
if (MyDslPackage.Literals.AELEMENT == eClass) {
return null;
}
return super.getAssociatedClusterType(eClass);
}
} public class MyDslRuntimeModule extends org.xtext.example.mydsl1.AbstractMyDslRuntimeModule {
public Class<? extends NamesAreUniqueValidationHelper> bindNamesAreUniqueValidationHelper() {
return MyDslNamesAreUniqueValidationHelper.class;
}
} @ComposedChecks(validators=NamesAreUniqueValidator)
class MyDslValidator extends AbstractMyDslValidator {
}
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de
|
|
|
Re: Customization of NamesAreUniqueValidator [message #1384130 is a reply to message #1383996] |
Wed, 28 May 2014 07:53 |
Alexander R Messages: 211 Registered: July 2013 |
Senior Member |
|
|
Hi,
I had enabled the composedCheck = "org.eclipse.xtext.validation.NamesAreUniqueValidator" in the workflow-file! After disabling it, your example works fine.
But what about nested elements?
Example: I disable the checking for operations ---> is the namechecking for nested elements of an operatin (parameters, local variables etc..) also disabled?
Thanks
[Updated on: Wed, 28 May 2014 08:10] Report message to a moderator
|
|
|
Powered by
FUDForum. Page generated in 0.04315 seconds