• Marcel (13/13) Oct 26 2019 I have a solution with the following folder layout:
• Rainer Schuetze (8/23) Oct 27 2019 Normally the semantic engine doesn't need the JSON files to analyze

Marcel <marcelpi97 gmail.com> writes:

I have a solution with the following folder layout:

- Solution A Folder:
     - foo.visualdproj
     - foo.d
     - bar.visualdproj
     - bar.d
     - JSON folder:
          - foo.json
          - bar.json

An external project imports both static libraries foo and bar 
(With the import path being the solution folder). Unfortunately 
intellisense doesn't work when importing these modules. I doubt 
this is an issue of VisualD so does anyone know what I'm missing?

Rainer Schuetze <r.sagitario gmx.de> writes:

On 26/10/2019 21:39, Marcel wrote:
 I have a solution with the following folder layout:
 
 - Solution A Folder:
     - foo.visualdproj
     - foo.d
     - bar.visualdproj
     - bar.d
     - JSON folder:
          - foo.json
          - bar.json
 
 An external project imports both static libraries foo and bar (With the
 import path being the solution folder). Unfortunately intellisense
 doesn't work when importing these modules. I doubt this is an issue of
 VisualD so does anyone know what I'm missing?

Normally the semantic engine doesn't need the JSON files to analyze
imports. The JSON files are only used if enabled in the global
intellisense options and the semantic engine didn't produce any result,
e.g. if there are no completions through existing imports.

If you want to include JSON files from projects not in the current
solution, you should add the respective path in the global option
"prebuilt browse information".