there involves a public api - I really didn't want to mess with the index map myself

I’m not sure myself but I’m intrigued. What’s the usecase?

its not trivial because the way the index is build, some indexes are accumulative and its hard to know if something was add multiple times by different resolvers/mutations, in that case it would require some full analysis to avoid removing something that might break the index

the simplest way is to re-build the index without the things you dont want

you can use the index-resolvers & index-mutations to do so, get everything there, remove what you dont want, and rebuild the index

alright, thanks!

@U3XCG2GBZ the use case is that I want to dynamically register user mutations and resolvers, and the final index should change given the context of that user