[feature] Join affected env with path separators

[KS-ZF]

Describe the bug

When using filegroups for environment variables, moonrepo passes a string where the different file paths are separated via comma ',' but not via the OS-Specific path separators e.g. ':' for POSIX or ';' for Windows
Because file separators are OS-Specific, this can lead to issues with programs expecting OS-Specific path separators, e.g. python programs using 'os.pathsep'.

Steps to reproduce

1. On Windows, create a moon.yml file with a fileGroup 'myFiles' and a task 'myTask'

  fileGroups:
    myFiles:
    - "/example_file_path/file_a.txt"
    - "/example_file_path/file_b.txt"
  
  tasks:
    myTask:
     command: echo
     args:
       - "$env:MY_FILE_PATHS"
     env:
        MY_FILE_PATHS: "@group(myFiles)"

2. Execute task 'myTask'
   Expected behavior
   moonrepo passes file paths separated by OS-Specific file separator to environment variable, therefore the terminal output on windows should be:
   myTask | ..\..\..\example_file_path\file_a.txt;..\..\..\example_file_path\file_b.txt

Screenshots

Environment
N/A

Additional context

N/A

[milesj]

This was never intended to use path separators, so I'm unsure if this is a bug or not.

[KS-ZF]

I was also not sure if a bug or feature request would fit better.
Because fileGroups can be used for environment variables and the current implementation causes problems with some applications expecting OS-specific separators, I chose the bug category.

Any recommendation for a configuration that is using fileGroups for environment variables and can be reused across windows and linux machines?

[milesj]

Is there a reason why you can't just parse the env var and format it to your needs?

[KS-ZF]

If you mean, that the application which is consuming the env var should handle the formatting, this is unfortunately not in our hands. It's a 3rd party application.

I do have a workaround/solution in place. I currently use something like this (Linus is untested so far:

fileGroups:
    myFilesWin:
      - >
         example_file_path\\file_a.txt;
         example_file_path\\file_b.txt

   myFilesLinux:
     - >
       example_file_path/file_a.txt:
       example_file_path/file_b.txt

tasks:
  myTaskWin:
     command: echo
     args:
       - "$env:MY_FILE_PATHS"
     env:
        MY_FILE_PATHS: "@group(myFilesWin)"
     options:
        os: 'windows'

  myTaskLinux:
     command: echo
     args:
       - "$env:MY_FILE_PATHS"
     env:
        MY_FILE_PATHS: "@group(myFilesLinux)"
     options:
        os: 'linux'

Therefore, If you don't see the costs/benefits in good relation, I don't mind if you close the ticket.

Best regards,
Kevin