Selecting one of suggested traits after "is" adds closing "]" about raml-suggestions HOT 4 CLOSED

@javok002, can not to reproduce, please provide more info, including at least your OS version and contents of '/exchange_modules/mulesoft-720/e2etrait_j3aczpxg882/1.0.0/trait.raml' file.

from raml-suggestions.

@dreamflyer I think that the problem is that the suggest after "is" is suggesting "secured" and it leaves an file with an error, because "is" expect to be an array:

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

/testResource:
  is:

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

/testResource:
  is: secured

It should suggest:

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

/testResource:
  is: [secured]

It works fine, if you have something like
is: [

the content of the trait is:

#%RAML 1.0 Trait
usage: Apply this to any method that needs to be secured
description: Some requests require authentication.

headers:
  access_token:
    displayName: token
    description: Access token
    example: "10"
    required: true
protocols: HTTP
queryParameters:
  name: string
responses:
  200:
    body:
      application/json:
        type: string
        examples:
          example1: SSSL
          example2: 1AA

from raml-suggestions.

@javok002,
in my case,
before applying suggestion:

after applying suggestion:

So, once again, i need following info(or at least most of that):

1. version of your OS.
2. version of your Atom(if you talking about Atom).
3. version of your Api-Workbench(if you talking about Api-Workbench).
4. list of installed Atom packages.

Also, if it possible, please attach screenshots or, even better, gif animation of issue reproduction.

from raml-suggestions.

We found that we where ignoring the extra property in the suggestion in the API designer, so it was not a bug.

from raml-suggestions.