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.

Sign up for GitHub

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

Jump to bottom

Inconsistent use of namespaceExists()-type functions in the registry db #824

Closed
jhiemstrawisc opened this issue Feb 16, 2024 · 0 comments · Fixed by #924
Closed

Inconsistent use of namespaceExists()-type functions in the registry db #824

jhiemstrawisc opened this issue Feb 16, 2024 · 0 comments · Fixed by #924
Assignees
@haoming29
Labels
bug Something isn't working registry Issue relating to the registry component
Milestone
v7.7.0

Comments

@jhiemstrawisc
Copy link
Member

As mentioned in #804, we're inconsistent about how we use these functions, and there are two nearly identical functions floating around -- namespaceExistsByPrefix() and namespaceExists(), which also takes a prefix. We should clean this up and settle on one or the other.
@haoming29 haoming29 self-assigned this Mar 6, 2024
@haoming29 haoming29 added this to the v7.7.0 milestone Mar 6, 2024
@haoming29 haoming29 added bug Something isn't working registry Issue relating to the registry component labels Mar 6, 2024
@haoming29 haoming29 mentioned this issue Mar 8, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@haoming29 haoming29

Labels
bug Something isn't working registry Issue relating to the registry component
Projects
None yet
Milestone
v7.7.0
Development

Successfully merging a pull request may close this issue.

Consolidate two namespaceExists DB function haoming29/pelican
2 participants
@haoming29 @jhiemstrawisc