Description
Namespacing pattern assumptions in URLs needs a revisit.
Organizations embedded in URLs are more of an exception, for example, Azure or GitLab (depending on how subgroups are implemented. It is up to the user though).
Unfortunately, there's too much room for mis-identification, and typical users need to think too hard to override the default behavior.
- As a user, my git provider does not embed organization in the URL. I expect the parser to handle my URLs as-is.
- As a user, I know my git provider uses organizations. I'd like to be able to give hints to the parser to find the organization.
Some kind of builder pattern that lets you give hints to the parser for a Git host may suffice?
I'm not sure what this looks like. I don't personally use any git providers that embed organizations in the URL, so more research or feedback from users is needed.
I think one of the main outcomes I want is to have some git provider specializations that are opt-in, since there are certain providers that use URL patterns that are unique. Perhaps this will help typical users.