You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A vajram can have atmost one fanout resolver per dependency
The vajram gradle plugin should load the vajrams in the module, create the graph and perform the validation, else fail build.
The text was updated successfully, but these errors were encountered:
This is not possible to do this in annotation processing phase because not all resolvers are defined using the resolve annotation. There are simple input resolvers written using the direct syntax. The only way to figure out all the resolvers defined in a vajram is to load the vajram classes and create vajrams/vajram metadata objects. These objects constructors already have the validations defined.
What this means is that we don't need to implement anything specific for validating the number of fanout resolvers as per is this issue. All we have to do is implement a way to create all vajrams as part of the build step. This should cover all validations and even future validations added to vajram metadata class.
Changing the issue title to reject this generic scope of this issue
RamAnvesh
changed the title
#MaxOneFanoutResolverPerDependency Add support validating the vajram post code generation phase
#RunAllRuntimeVajramValidationsDuringBuildTime Add support validating the vajram post code generation phase
Feb 6, 2025
A vajram can have atmost one fanout resolver per dependency
The vajram gradle plugin should load the vajrams in the module, create the graph and perform the validation, else fail build.
The text was updated successfully, but these errors were encountered: