When autocompleting a path for an include, it would be good that since you are always targeting files it automatically added the last slash to the insetText.
For instance:

• Having this filedirectory/file.raml
• And asking for suggestions in: !include
• Will return insertText: directory/ instead of just directory
• End result will be: !include directory/, so asking for suggestions again will return file.raml, making it faster to complete a path.

Having this:

/:

It does not suggest nothing under the /:.
I should suggests methods, parameters or any other.

This will already suggest get:

/:
  g

When there is an example node, inside of a type or a response, the following line does not have any suggestions, but it should. In the case that the caret in two lines below the example it works fine.
This is the case that doesn't work:

This are the suggestions it should provide:

#%RAML 1.0 Library

types:
  TestEnum:
    type: string
    enum: [one, two]
    example: one

annotationTypes:
  TestAnnotation: TestEnum

resourceTypes:
  AnnotatedResource:
    (TestAnnotation): one

There is no completion for one value in (TestAnnotation): one

RAML:

#%RAML 1.0 Api

types:
  TestEnum:
    type: string
    enum: [one, two]
    example: one

There is no completion for one value in example: one

Same for

types:
  TestEnum:
    type: string
    enum: [one, two]
    example: one
  TestType2:
    properties: 
      prop: TestEnum
    example: 
      prop: one

prop: one

The problem is reported in an issue in the api-designer, but the suggestion is generated in this module. This is the issue: mulesoft/api-designer#433 (comment)

Having the next files:

dataTypeA.raml:

type: object
properties:
  name:
    required: true
    type: string
  age:
    required: false
    type: number
  /^note\d+$/: # restrict any properties whose keys start with "note"
                # followed by a string of one or more digits
    type: string

dataTypeB.raml:

type: !include dataTypeA.raml
properties: 
  employeeNo: string

And a api.raml containing:

  get:
    responses: 
      200:
        body: 
          application/json:
            type: !include dataTypeB.raml
            example:
              employeeNo: 2oo

Suggestions under example node does not include name, nor age properties, the only suggestion is employeeNo, nevertheless the parser validates missing name property since it has been defined as required.

In the following example:

#%RAML 1.0
title: testShelf

/resourceName:
  #Point 4
  get:
    #POINT 1
    responses: 
      200:
        body: 
          application/json:
            type: string 
        headers:
          Content-Encoding:
            type: object
    #POINT 2
    #POINT 3
  #POINT 5
  #POINT 6

When situated at #Point 1 suggestions displayed in the shelf panel are not the same as those when situated at #Point 2, despite being at the same level.

However, when situated at #Point 3, suggestions are correctly displayed as in# Point 1.

This issue also occurs at "get" level with #Point 4, 5 and 6.

When a trait suggestion after a 'is' selected the closing ']' is added but there ir no opening '['

With this example:

#%RAML 1.0
title: testConsumeFragment
traits: 
 secured: !include /exchange_modules/mulesoft-720/e2etrait_j3aczpxg882/1.0.0/trait.raml
/testResource:
  is: s

If you suggest after the last char, and select the 'secured' option, the text to insert is 'secured]', which results in this:

#%RAML 1.0
title: testConsumeFragment
traits: 
 secured: !include /exchange_modules/mulesoft-720/e2etrait_j3aczpxg882/1.0.0/trait.raml

/testResource:
  is: secured]

Having the following raml fragment and raml specification:

DataTypeA.raml

type: object
properties:
  name:
    required: true
    type: string
  age:
    required: false
    type: number
  /^note\d+$/: # restrict any properties whose keys start with "note"
                # followed by a string of one or more digits
    type: string

Then created another raml fragment named DataTypeB.raml
DataTypeB.raml

type: !include dataTypeA.raml
properties: 
  employeeNo: string

Then, create an api that includes dataTypeB for a response type e.g.:

/resource:
  get:
    responses: 
      200:
        body: 
          application/json:
            type: !include dataTypeB.raml
            example:
              employeeNo: 2oo

When we invoke suggestions under example node, it does not include name, nor age properties, the only suggestion is employeeNo. Nevertheless the parser validates missing name property since it has been defined as required

It would be great to have a suggestion to reference an external file using !include.

Although when declaring a type the include external file is not suggested, when writing '!in' the include option is suggested as shown here:

It would be great to have this suggestion at first

I've notice when there is a node with a value and a new value is suggested, the result of adding this suggested value is an invalid.

Here it happened in in protocols (Here more protocols can be added as a list, but is not the suggested case):

Here with a type inside a response: