After changes 05f3877df7ea0b8f4a8c95a8cc3ba588a57cbb2e and 549174d83c3b5015755b0dfab5b4b5e480b8e394SvelteJSReferenceExpressionResolver and SvelteTypeScriptReferenceExpressionResolver should be adapted to the new API.
To keep them working in the previous way, one of the option is to remove override from SvelteTypeScriptReferenceExpressionResolver.createLocalResolveProcessor, and in SvelteJSReferenceExpressionResolver.resolve make it work similar to how it's done in SvelteTypeScriptReferenceExpressionResolver, i.e. if resolve is local, call createLocalResolveProcessor (also need to remove override there).
ulitink
commented
2 years ago
After changes
05f3877df7ea0b8f4a8c95a8cc3ba588a57cbb2eand549174d83c3b5015755b0dfab5b4b5e480b8e394SvelteJSReferenceExpressionResolverandSvelteTypeScriptReferenceExpressionResolvershould be adapted to the new API.To keep them working in the previous way, one of the option is to remove override from
SvelteTypeScriptReferenceExpressionResolver.createLocalResolveProcessor, and inSvelteJSReferenceExpressionResolver.resolvemake it work similar to how it's done inSvelteTypeScriptReferenceExpressionResolver, i.e. if resolve is local, callcreateLocalResolveProcessor(also need to remove override there).