[Bug] Using a `/` in an Environment Name causes error

[christopher-nash]

I ran into this while attempting to import a Postman Environment. I had an environment I called "Beta / Staging" in Postman which would result in an An error occurred while importing the environment. After some experimenting with the json I removed the / character and it imported fine.

To reproduce:

1. Click Configure for the environments
2. Click + Create
3. Set the Environment Name to Some / Thing (any name which includes a / will cause the error)
4. Click the Create button
5. Note the error An error occurred while created the environment is displayed

Setting the environment to include other special characters such as ~ or = or even \ works fine. It only appears to happen with /.

I tried looking in the developer console and I don't see any errors showing up there. I'm not sure where to go looking for generated log files that might give additional details on the actual error root cause.

[leeclarke]

I encountered the same issue with a colon as well in the title. Snippet of the environment file I was trying to import: I edited the file and removed the the ":" and it imported to verify it was the colon

{
	"id": "af02b0ad-2048-1f15-b544-e8011d2e0ca7",
	"name": "3: CAT",
	"values": [
		{
			"key": "base_url",
			"value": "https://example.com/",
			"enabled": true
		},
	 ]
}

[end3rbyte]

Fixed for any character not allowed in filenames