-
Task
-
Resolution: Unresolved
-
P2: Important
-
None
-
None
-
21
-
4b18f5270 (dev), 5d5e46536 (dev), a39e32ec7 (dev)
-
Foundation Sprint 138, Foundation Sprint 139, Foundation Sprint 140, Foundation Sprint 141, Foundation Sprint 142
There are a few classes that don't belong to the data infrastructure, but serve as a piece of helpers infrastructure.
For example files bellow:
HttpFileElement HttpRequiest ServerVariable helpers-body/header
In other words, it doesn't matter what user defines in *.yaml file for generation, these files from the list above will be generated exactly as it is and included into the resulting Qt6 Client library.
More over, if user wants to link 2 different Qt6 Client libraries generated from 2 different *.yaml files, resulting application will have a problem with symbols duplications because of these files.
Currently, the problem is being solved by putting each library under own namespace name on the generation step.
But also we can optimize the usage by moving duplicated logic into a separate library.
And use this "common" library from each Qt6 Client library.
| For Gerrit Dashboard: QTBUG-140233 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 680870,21 | Add options to manage the common files | dev | qt/qtopenapi | Status: MERGED | +2 | 0 |
| 682648,2 | Move commonly used mustache files to a separate folder | dev | qt/qtopenapi | Status: MERGED | +2 | 0 |
| 686112,5 | Re-generate all test clients with 'Use-Common-Lib' option | dev | qt/qtopenapi | Status: MERGED | +2 | +1 |