# \#custom-resolver

**URL:** https://discuss.dgraph.io/tag/custom-resolver/221.md

[Latest](https://discuss.dgraph.io/latest.md) · [Categories](https://discuss.dgraph.io/categories.md) · [Tags](https://discuss.dgraph.io/tags.md)

---

## [Status on Missing Custom Features](https://discuss.dgraph.io/t/status-on-missing-custom-features/16229)

<div class="topic-metadata">

**Author:** [@jdgamble555](https://discuss.dgraph.io/u/jdgamble555)\
**Replies:** 0\
**Last updated:** [December 4, 2021, 9:07pm UTC](https://discuss.dgraph.io/t/status-on-missing-custom-features/16229 "2021-12-04T21:07:28Z")

</div>

The Custom and Lambda directive are very powerful, however they are not complete. I want to first be clear that I do not want to just complain about EVERY missing feature request. I just keep trying to build a real usa…

---

## [Suggestion on adding new query and mutations on top of default scehma](https://discuss.dgraph.io/t/suggestion-on-adding-new-query-and-mutations-on-top-of-default-scehma/10658)

<div class="topic-metadata">

**Author:** [@dgandhi17](https://discuss.dgraph.io/u/dgandhi17)\
**Replies:** 13\
**Last updated:** [October 2, 2020, 12:12pm UTC](https://discuss.dgraph.io/t/suggestion-on-adding-new-query-and-mutations-on-top-of-default-scehma/10658 "2020-10-02T12:12:46Z")

</div>

As dgraph already is Graphql I want to have custom queries and mutation for 3rd party endpoint. like login to third party services have data in our dgraph. Kinda hybrid approach so that only the queries and mutation for…