-
Notifications
You must be signed in to change notification settings - Fork 29
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
Fully handle layer namespace #19
Milestone
Comments
ocourtin
pushed a commit
that referenced
this issue
Nov 4, 2012
ocourtin
pushed a commit
that referenced
this issue
Nov 4, 2012
ocourtin
pushed a commit
that referenced
this issue
Nov 5, 2012
ocourtin
pushed a commit
that referenced
this issue
Nov 5, 2012
ocourtin
pushed a commit
that referenced
this issue
Nov 5, 2012
Still an open ticket as i still need to:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now several internal functions assume that layer name is unique, and don't care about related namespace (even if namespace is already retrieved in storage structure)
From userland this lead to be able to retrieve a layer even if namespace prefix or uri is wrong, and to not been able to handle several layers having same name in several namespaces.
Quite a big issue, as it imply code refactoring.
The text was updated successfully, but these errors were encountered: