Description Christian Damus 2019-11-05 16:56:31 EST

The ValidationService (the view-model service one, not the core one) allows injection of diagnostics via ValidationProviders, including registration of such providers on an extension point.

In my private client application, I need to register a ValidationProvider but this provider needs additional services from the context.  However, the ValidationProvider protocol is only asked to provide a list of diagnostics for an EObject without any other context:

    List<Diagnostic> validate(EObject eObject);

(from Validator in the core).

Even if the view model context could be inferred from the EObject in some cases, in others it may not be inferrable (e.g., if it's an object in the EPackage registry).  And besides, it would be nice for a provider to be called back when it is added to the ValidationService to tell it what the context is, so that it can set up dependencies.