entities in request always empty

I’m submitting a…

• Bug report
• Feature request
• [ x ] Documentation issue or request
• Other… Please describe:

Expected Behavior

If i set an entity in my language model it should be filled up with a value when the request is sent.

Current Behavior

I’m trying to migrate my v3 project to v4 and everything works fine beside migrating my inputs to v4. I adjusted the language model as described in the documentation and this is how my intent looks right now:

"SetupUsernameIntent": {
        "phrases": [  "{name}",
          "my name is {name}",
          "i am {name}",
          "you can call me {name}"],
        "entities": {
          "name": {
            "type": {
              "alexa": "AMAZON.US_FIRST_NAME",
              "dialogflow": "@sys.given-name"
            }
          }
        }
      }

This is how my intent handler looks:

@Intents('SetupUsernameIntent')
setupUsername(){
    console.log(this.$entities);
}

However this.$entities is always empty if i do for example my name is John. I also see that in the Debugger in the lifecycle that now entities are being added.

What am i doing wrong? My example is pretty much the same as in documentation.

PS: the right intent is triggered, so the routing works

Your Environment

• Jovo Framework version used: 4.0.0
• Operating System: MacOS, Firefox

[m-ripper]

Hey @EeeDotZee, I am glad that I could help even if the dynamic part didn’t work. I will take a look into this.

Regarding the typings of nlpjs I agree, that’s something we’re going to add in the near future as well. Sadly, nlpjs is written in javascript and does not provide typings itself, but we can go through the code and type the most important parts, it just had a low priority so far.

It’s definitely helpful, thank you for your feedback!

[tfrenken]

Sorry for reopening this but are there any updates on enabling the debugger to auto-fill entities?

The workaround with a custom entity type for the debugger works for me, the small hack proposed my @m-ripper does not - although I am trying to extract a search query, not a name.

Being able to have the debugger’s NLP auto extract entities would be really nice!