I have a method, which gets passed a Foundset (based on a Relation) as parameter. The method is in a Base-Solution which is used as a module for different Solutions.
If I declare the parameter with JSDoc as ```
@param {JSFoundsetdb:/omsv_base/base_sprachwerte} relationsObj
I've tried out as described in the wiki to declare the fields like ```
@param {JSFoundset<{sprachwerte_id:String, sv_owner:String, stammtbl_id:String, stammtbl_name:String, sprache:String, textkurz:String, textlang:String, textmaxi:String, adduser:String, adddate:DateTime, mutuser:String, mutdate:DateTime}>} relationsObj
```But even so I get a warning.
How do I declare the parameters exactly, that JSDoc dont give a warning?
you could try:
@param {JSFoundset<db:/omsv_base/base_sprachwerte>|JSFoundset<db:/omsv_xxx/base_sprachwerte>} relationsObj
Yes, this works. Thanks.
This means also, however, if we develop a new solution we have to define the new server for this solution on all this methods.
Just for my understanding, why does not work the version with the field declaration as shown in my second example code?
that is just not supported for the JFoundset type, that is a very special syntax that we have to write build in support for.
Why are you using constantly a new database for the same thing?
I have a solution with base functionality. In some times, this functionality is based on tables. That for I have a base database with only this base tables. The JSDoc declarations all use this database (server).
This base solutuion will be added to all our solutions as module. All solutions has their own database with many tables, include the base tables.
Because we have more than one big solution we are not able to lift all this solutions at the same time to a new version. So it can be, that solution 1 needs a older version of the base functionaltiy then solution 2. That for we add the base solution to each solution as a ‘copy’ of the base solution with a different name.