hey! now that we have the intellij plugin, is ther...

# apollo-kotlin

[agrosner]

hey! now that we have the intellij plugin, is there any plans to introduce linting around unused graphql fields? you know the usages of the graphql + generated kotlin files. now if the next step to discover unused field references

[Ryan Brink]

wouldn't that only work under the assumption that that particular app was the only consumer of the api?

[agrosner]

Correct!

[bod]

Yes! Totally under our radar 🙂 At the moment I haven't found a way to implement "Find usages" on operation fields (which is a similar mechanism), but we want to have it.

[bod]

Hello, World! In the latest weekly snapshot, unused operations and fields are detected and shown in grey 🙂 If you have the chance to test it, feedback is appreciated!

[Ryan Brink]

The use case feels kinda limited IMO, since it relies on the idea that you are the sole consumer of the API. Is there a way to turn this off for people who don't want this?

[bod]

Is there a way to turn this off for people who don't want this?

yes, it's in the inspections settings (you can access it from the warning itself)

[bod]

Screenshot 2023-07-10 at 14.05.48.png

[Ryan Brink]

OH i see... you guys show this for the queries... that makes sense! For some reason, I had it in my head that you showed this on the schema (if that was present in the repo). I'm on board now 🫡 🫡

[bod]

ahhh yes I can see how you could think that! 🙂

[bod]

(your remark still makes sense, if you're building a library, then consumers of the operation can be in other projects that the plugin isn't aware of)

[agrosner]

Woah!!! I’ll have to give it a spin

[agrosner]

This will be hugely useful for our 300+ module app as we migrate from gson, reflection, and an in house graphql system where response models were shared 🤪 and we didn’t know what was truly used or not without a lot of investigation . It’ll help keep our queries and code optimized

[bod]

very cool! I hope it'll work as expected 🤞