How to filter suggestions? about monaco-editor HOT 26 CLOSED

I'm controlling this API but I know no straightforward way of removing _ layer.

But I'm certainly sure we are not the only API relying on this pattern.

So for all of these API we need to develop a tool to "clean" the definition file

from monaco-editor.

This might be helpful specifically for TypeScript.

from monaco-editor.

@jrieken @joaomoreno Do you know how/if this is feasible to add to the API ?

from monaco-editor.

That's not possible unless you tackle the provider of the suggestions, say TypeScript language service etc

from monaco-editor.

It was possible in the preview versions

from monaco-editor.

up?

from monaco-editor.

@deltakosh It is still not possible unless you use your own provider. Do you need help to implement/add your own provider?

from monaco-editor.

Any help would be greatly appreciated:) I just need the regular provider without _ properties and functions

from monaco-editor.

I just need the regular provider without _ properties and functions

Do I assume correctly that you have added a some_lib.d.ts file that defines such symbols? Iff so why is it like that?

from monaco-editor.

We added a custom d.ts where _ define private properties and functions

from monaco-editor.

where _ define private properties and functions

So, why adding them and then filtering them again?

from monaco-editor.

Do you really suggest that I manually remove all _properties from my d.ts?
Here is the file: https://github.com/BabylonJS/Babylon.js/blob/master/dist/babylon.2.4.d.ts

from monaco-editor.

No, my question is why does the d.ts contains symbols with _ if those aren't desired. Do you control that API? Is it just a file you need to process? Is the API two fold and public layer and a private aka _ layer?

You are failing to motivate why we should enable to filter suggestions globally in the editor while it seems to be you that's controlling those suggestions anyways?

from monaco-editor.

Note: Some _ must be flagged as public as there is no internal in TS

from monaco-editor.

Any thoughts?

from monaco-editor.

I guess I failed to explain my issue. Se please let me try again:

• we are generating our Babylon.d.ts from our typescript source files
• private properties are by convention preceded by a _
• unfortunately as there is no internal keyword in typescript, we have to flag some _ properties as public

Hopefully this is clearer now:)

from monaco-editor.

up?

from monaco-editor.

up?

from monaco-editor.

Do you have news on this?

from monaco-editor.

I'm also interested in this feature! Any news on that?

from monaco-editor.

Right ! Do you have any news about that ?

from monaco-editor.

I have the same issue, any ETA ?

from monaco-editor.

Note: Some _ must be flagged as public as there is no internal in TS

TypeScript compiler supports stripInternal option. It should work in your case.
http://www.typescriptlang.org/docs/handbook/compiler-options.html

from monaco-editor.

The problem is that babylon.js library is pretty big now and adding /** @internal */ JSDoc annotation to all _ properties and methods is not an option

from monaco-editor.

Apparently the 0.18 is now displaying properties flagged as private. Is that expected?

from monaco-editor.

In my case I just want to remove the undefined option from the list, without disabling variables. Don't want to implement a completion provider just to filter out one item from the list.

from monaco-editor.