# Using the @lang field in Slash GraphQL

**URL:** <https://discuss.dgraph.io/t/using-the-lang-field-in-slash-graphql/13154>\
**Category:** GraphQL\
**Tags:** kind:question\
**Created:** [March 11, 2021, 9:55am UTC](https://discuss.dgraph.io/t/using-the-lang-field-in-slash-graphql/13154 "2021-03-11T09:55:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![charklewis](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/charklewis/32/6282_2.png) [@charklewis](https://discuss.dgraph.io/u/charklewis)\
**Post date:** [March 11, 2021, 9:55am UTC](https://discuss.dgraph.io/t/using-the-lang-field-in-slash-graphql/13154/1 "2021-03-11T09:55:28Z")

</div>

I am exploring how to implement multi-language strings as this is a big part of my database. I have come across the [Get Started with Dgraph - Multi-language strings](https://dgraph.io/docs/master/tutorial-4/#) tutorial which shows a nice solution to this.

I am new to creating back end GraphQL schemas and Dgraph, soI likely have am missing some knowledge or have a misunderstanding of how this could work.

From what I can understand the @lang is a Dgraph specific directive and doesn’t belong to native GraphQL. With this in mind, is it possible to use the Lamdba functions to resolve a query that can use these Dgraph enhancements?

As a very basic example, I am trying to achieve the following:

```auto
type Entry {
  id: ID! 
  title: String!
  description: String!
}

```

Where both title and description are multi-language fields. And to get the correct result I could query:

```auto
query MyQuery {
  getEntry(id: "123", lang: "en") {
    title
    description
  }
}

```

And in the lambda function it would return the correct `title@en`, `description@en` etc.

Is this possible?

---

<div class="post-metadata">

**Author:** ![JatinDevDG](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/jatindevdg/32/3417_2.png) [@JatinDevDG](https://discuss.dgraph.io/u/JatinDevDG)\
**Post date:** [March 11, 2021, 10:14am UTC](https://discuss.dgraph.io/t/using-the-lang-field-in-slash-graphql/13154/2 "2021-03-11T10:14:21Z")

</div>

Hi @charklewis, We are working on supporting multi-language fields in GraphQL and will have them soon.  
We already have RFC for this feature [[WIP]RFC: Allow language Tag support in GraphQl - #6 by amaster507](http://discuss.hypermode.com/t/wip-rfc-allow-language-tag-support-in-graphql/13027/6)

---

<div class="post-metadata">

**Author:** ![charklewis](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/charklewis/32/6282_2.png) [@charklewis](https://discuss.dgraph.io/u/charklewis)\
**Post date:** [March 11, 2021, 11:19am UTC](https://discuss.dgraph.io/t/using-the-lang-field-in-slash-graphql/13154/3 "2021-03-11T11:19:31Z")

</div>

Ah ok thanks! Is there a solution you recommend while waiting for this feature to be ready? I’m thinking at the moment use a schema that doesn’t have translations.

Is the feature close to being released?

---

<div class="post-metadata">

**Author:** ![JatinDevDG](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/jatindevdg/32/3417_2.png) [@JatinDevDG](https://discuss.dgraph.io/u/JatinDevDG)\
**Post date:** [March 11, 2021, 11:31am UTC](https://discuss.dgraph.io/t/using-the-lang-field-in-slash-graphql/13154/4 "2021-03-11T11:31:23Z")

</div>

We will add this by this month in master branch and it will be part of 21.07 release.  
Sorry, currently there is no workaround for this. You have to use schema that doesn’t have multi language fields.