agtdatalake opened a new issue, #5769:
URL: https://github.com/apache/hop/issues/5769
### What would you like to happen?
Gostaria de Sugerir uma mudança no hop-config.json
Currently, the configuration file paths are written linearly in the
configurationFiles key:
[ "${PROJECT_HOME}/env/prd/citrus_cropwise.json",
"${PROJECT_HOME}/env/prd/database_agtdw.json",
"${PROJECT_HOME}/env/prd/database_agtportal.json",
"${PROJECT_HOME}/env/prd/database_arcgis.json",
"${PROJECT_HOME}/env/prd/database_ebs.json",
"${PROJECT_HOME}/env/prd/database_glpi.json",
"${PROJECT_HOME}/env/prd/database_mysql.json",
"${PROJECT_HOME}/env/prd/database_pims.json",
"${PROJECT_HOME}/env/prd/database_pims_agtcoa.json",
"${PROJECT_HOME}/env/prd/database_pims_mobilidade.json",
"${PROJECT_HOME}/env/prd/database_senior.json",
"${PROJECT_HOME}/env/prd/database_tgc_tgr.json",
"${PROJECT_HOME}/env/prd/enviar_email.json",
"${PROJECT_HOME}/env/prd/ftp.json", "${PROJECT_HOME}/env/prd/fulltime.json",
"${PROJECT_HOME}/env/prd/gupy.json",
"${PROJECT_HOME}/env/prd/integracao_mastersaf_nfe.json",
"${PROJECT_HOME}/env/prd/integracao_micromap.json",
"${PROJECT_HOME}/env/prd/outros.json",
"${PROJECT_HOME}/env/prd/integracao_estacao_zeus.json",
"${PROJECT_HOME}/env/prd/ldap.json", "${PROJE
CT_HOME}/env/prd/arcgis.json" ]
the above approach has caused problems in versioning with multiple
development teams..
I would like to suggest that each time a configuration is added, a line
break is performed, improving versioning.
before
<img width="1603" height="198" alt="Image"
src="https://github.com/user-attachments/assets/dfdaab5c-8341-4423-9746-9d709c0f580d";
/>
after
<img width="1016" height="807" alt="Image"
src="https://github.com/user-attachments/assets/71bd86f1-9e4e-47a0-a94b-e634e44e13f3";
/>
### Issue Priority
Priority: 3
### Issue Component
Component: Hop Config
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
