Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Perforce workspace name and dir separation #16

Open
2 tasks done
antirotor opened this issue Oct 24, 2024 · 0 comments
Open
2 tasks done

Perforce workspace name and dir separation #16

antirotor opened this issue Oct 24, 2024 · 0 comments
Labels
sponsored This is directly sponsored by a client or community member

Comments

@antirotor
Copy link
Member

Is there an existing issue for this?

  • I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?

The workspace is now determined from the workspace dir Site settings. This assumes that directory where the workspace is is the same as its name, but this might not be the case in all cases and if using the streams, you might want to have workspace per stream.

How would you imagine the implementation of the feature?

We should change the settings so you can specify workspace name and stream name as template {host_name}_{project_code}_{user_name} (that somewhat follows Perforce default behavior except the user_name is replaced by random number). Then all call needing workspace should call library function that will format this template and return it back.

Are there any labels you wish to add?

  • I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

No response

Additional context:

No response

@antirotor antirotor added type: enhancement Improvement of existing functionality or minor addition sponsored This is directly sponsored by a client or community member labels Oct 24, 2024
@dee-ynput dee-ynput removed the type: enhancement Improvement of existing functionality or minor addition label Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sponsored This is directly sponsored by a client or community member
Projects
None yet
Development

No branches or pull requests

2 participants