For Appsody projects, we can't get away with binding due to how Appsody is currently implemented. As a result, we still require binding and creation of Appsody projects to be in the codewind-workspace directory. We choose this workspace to make the migration scenario easier for 0.5.0 to 0.6.0, since we don't want to move the user projects to a new directory.
Closing as the codewind-workspace isn't needed, a codewind-data is created instead and we need to let the user not to use that directory as it is special.
For Appsody projects, we can't get away with binding due to how Appsody is currently implemented. As a result, we still require binding and creation of Appsody projects to be in the codewind-workspace directory. We choose this workspace to make the migration scenario easier for 0.5.0 to 0.6.0, since we don't want to move the user projects to a new directory.