feat: Language-Understanding LSP

[Shuai Wang (cosmicshuai)]

Description

An LSP implementation for language-understanding language features in composer

Language feature checklist

• syntax highlighting for intent, utterance, entities;
  

• Validation lu file

  • syntax errors
  • semantic errors

• Auto-suggestion for creating entities

  • suggest entity types, hasRoles and useFeature
    
    
    

  • auto suggest prebuilt entities
    

  • auto suggest composite entities
    

  • auto suggest regex entities
    

• Auto suggest, auto complete experience for writing patterns in utterance
  
  

• Auto complete when user typing in list entity
  

• auto complete in ml entities
  

• Labeling Experience
  Auto adding unlabeled entity when user hit Shift + Enter,
  

Task Item

refs #867

Screenshots

Please include screenshots or gifs if your PR include UX changes.

[github-actions]

Coverage decreased (-0.3%) to 42.756% when pulling e1f402e on shuwan/AddLu_LSP into cfb4b77 on master.

[Vishwac Sena Kannan (vishwacsena)]

Dong Lei (@boydc2014)

Few things observed when I played with this

1. Entity auto-suggest/ auto-complete does not work for utterances that appear above the entity definition. In example below, adding a { in one of the two utterances does not bring up entity auto suggest/ completion flyout. However I do see this on { in intent/ utterances added after the entity definition. Entities are tied to the application and so the position where they are defined should not matter.

# foo bar intent
- this is a test utterance with
- this is another utterance with 

@ ml simple1
@ prebuilt  age  hasRoles userAge

2. We appear to insert additional space before usesFeature and hasRoles when selecting these options from auto-suggest. Notice the extra space before hasRoles in the auto-completed example above for prebuilt entity age
3. Roles do not need @ notation for suggestions to show up in auto-suggest/ auto-complete. We should just show this when we show other entity suggestions when labelling.

[Shuai Wang (cosmicshuai)]

Dong Lei (@boydc2014)

Few things observed when I played with this

1. Entity auto-suggest/ auto-complete does not work for utterances that appear above the entity definition. In example below, adding a { in one of the two utterances does not bring up entity auto suggest/ completion flyout. However I do see this on { in intent/ utterances added after the entity definition. Entities are tied to the application and so the position where they are defined should not matter.

# foo bar intent
- this is a test utterance with
- this is another utterance with 

@ ml simple1
@ prebuilt  age  hasRoles userAge

1. We appear to insert additional space before usesFeature and hasRoles when selecting these options from auto-suggest. Notice the extra space before hasRoles in the auto-completed example above for prebuilt entity age
2. Roles do not need @ notation for suggestions to show up in auto-suggest/ auto-complete. We should just show this when we show other entity suggestions when labelling.

Dong Lei (@boydc2014)

Few things observed when I played with this

1. Entity auto-suggest/ auto-complete does not work for utterances that appear above the entity definition. In example below, adding a { in one of the two utterances does not bring up entity auto suggest/ completion flyout. However I do see this on { in intent/ utterances added after the entity definition. Entities are tied to the application and so the position where they are defined should not matter.

# foo bar intent
- this is a test utterance with
- this is another utterance with 

@ ml simple1
@ prebuilt  age  hasRoles userAge

1. We appear to insert additional space before usesFeature and hasRoles when selecting these options from auto-suggest. Notice the extra space before hasRoles in the auto-completed example above for prebuilt entity age
2. Roles do not need @ notation for suggestions to show up in auto-suggest/ auto-complete. We should just show this when we show other entity suggestions when labelling.

I will look into it and fix the problems.

[Shuai Wang (cosmicshuai)]

Chris Whitten (@cwhitten) I've already fixed your comments and some test cases for the utility functions are added.

[Chris Whitten (cwhitten)]

Nice work!

[TylerOdenthal]

Congratz on pushing this out with v1.0.2! Just got the update and noticed the change.