IDEMSInternational / open-app-builder

PLH App Frontend
GNU General Public License v3.0
5 stars 24 forks source link

[BUG] Deployment config inheritance – relative paths do not inherit correctly #2330

Open jfmcquade opened 1 month ago

jfmcquade commented 1 month ago

Describe the bug When a deployment config has a parent deployment, property values that refer to relative paths do not inherit correctly: the path as it appears in the value of the property in the final compiled deployment config is the absolute path calculated from the relative path relative to the parent deployment, instead of the child deployment.

For example, the plh_kids deployment specifies the value of the app data output path as follows:

config.app_data.output_path = "./app_data";

The plh_kids deployment has a child deployment, plh_kids_kw. The expected behaviour would be that the output path for the child deployment would be calculated as relative to the child deployment folder, and so the child deployment need not specify a value for the app data output path. However, without specifying its own value, the app data output path for the compiled child deployment is set to the path to the app data output folder within the parent deployment's deployment folder. This can be worked around by adding the line above to the child deployment config file.