Laravel-backup: Google drive backup fails when folder name has underscores

[holymp2006]

...
"laravel/framework": "5.5.*",
"spatie/laravel-backup": "^5.0.0",
...

I've been using Google drive as my default backup disk, and it's been working fine.
Today I tried using a new folder on Google drive, but got an error.

Copying zip failed because: {
 "error": {
  "errors": [
   {
    ...
   }
  ],
  "code": 404,
  "message": "File not found: xxxxxx-xxxxx-xxxxx."
 }
}

The name of the old folder was just alphanumeric, so all worked well.
The name of the new folder I set is something like xxxxxx_xxxxx_xxxxx (with underscores).
The package seems to be renaming the folder to xxxxxx-xxxxx-xxxxx, causing the backup to fail when it tries to copy to Google drive - where xxxxxx-xxxxx-xxxxx obviously doesn't exist.

Is this the required behaviour?
If yes, please how can I change this behaviour on my own?

[oriceon]

Hi @holymp2006. I created a #917 pull request to solve the google drive backup issues but @freekmurze considered it unnecessary...

Anyhow, see what i changed in src/BackupDestination/BackupDestination.php

[holymp2006]

Thank you @oriceon, I'll make the recommended changes.

[smartsyncio]

Having a readable folder name makes much more sense than having to use googles gibberish.

Thank you :)

[spatie-bot]

Dear contributor,

because this issue seems to be inactive for quite some time now, I've automatically closed it. If you feel this issue deserves some attention from my human colleagues feel free to reopen it.