Allow for specific gong stage per diagram package

[thomaspeugeot]

Currently, the code uses GetDefaultStage() API to access gong stage.

It will be a problem when 2 gongdoc stacks deal with different gong models.

Steps:

• [x] set up another model (dummy)
• [x] fetch all GetDefaultStage() occurences
  • [x] add a stage paramter into modelPkg, _ := gong_models.LoadSource(absPkgPath) in gong
  • [x] add 2 stages paramters to diagramPackage, _ := load.LoadDiagramPackage(absPkgPath, modelPkg, *editable)
• [ ] in the main.go, add multiple agrs for fetching multiple stacks `gongdoc geometry/go/models dummy/go/models' and this makes the front with two diagrams editors
  • [ ] create a service that provides the list of stacks http://[localhost:8080/api/stacks](http://localhost:8080/api/stacks)
  • [ ] it in main app, creates a component that takes all the elements of the current app component and calls it from the app component
  • [ ] in the front main app, fetch all stacks and instanciates

[thomaspeugeot]

test

localhost:8080/api/github.com/fullstack-lang/gongdoc/go/v1/classdiagrams?GONG__StackPath='github.com/fullstack-lang/gongdoc/go/tests/geometry/go/models'

shows that stacks are correctly initialized

http://localhost:8080/api/github.com/fullstack-lang/gong/go/v1/gongstructs?GONG__StackPath=github.com/fullstack-lang/gongdoc/go/tests/geometry/go/models

[thomaspeugeot]

Now, one have to path the GONG_StackPath to tree component and then to the classdiagram component

[thomaspeugeot]

problem, the pkgEltDocument has an init BEFORE the init of the AppComponent. Therefore, when

<lib-pkgelt-docs [GONG__StackPath]="soloStack"></lib-pkgelt-docs>

soloStack is not set

[thomaspeugeot]

Ok, now the classdiagram component is initialized but difficult to know why "lazy" ?

The tree does not display correctly. investigation.

[thomaspeugeot]

Ok we know the problem, the front repo is loaded 3 times. 2 times with the correct GONG_StackPath and 1 time with an incorrect GONG__StackPath (because the classdiagram component is initialized for an unkown reason).

the problem is that the front repo is a singloton, therefore, a pull will overwrite the singloton the a pull that was done with a former path.

Steps:

• [x] check why gong/test2 did work with 2 stack instances. Does it not uses the FrontRepo ?
• [x] have the FrontRepo not use a singloton.

[thomaspeugeot]

Progress. Now, the front repo is correct. Problem, there are only four nodes.

In the back, we investiguate. OK, now forcing stage parameter on all generated API

[thomaspeugeot]

Still a problem. A node does not exist in the back end. This an updateNode and stack path is empty. This must be a problem in the front.

Tree is OK. Still problems with Classdiagram