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

Max 10 packages per scope? #4338

Closed
2 of 6 tasks
mvriel opened this issue Oct 23, 2023 · 4 comments
Closed
2 of 6 tasks

Max 10 packages per scope? #4338

mvriel opened this issue Oct 23, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@mvriel
Copy link
Contributor

mvriel commented Oct 23, 2023

Bug report

Bug category

  • Website: issues related to browse or discover packages.
  • Pipelines: issues related to publish or manage a package.
  • Registry: issues related to the registry server.
  • Unity Editor: issues related to how OpenUPM works with the Unity Editor.
  • Documentation
  • Others

Steps to reproduce

Add eu.netherlands3d as a scope to the Scoped Registries in Project Settings and see that eu.netherlands3d.tiles3d is missing in "My Registries"; add eu.netherlands3d.tiles3d as an additional scope and see it is present.

What is expected?

With the scope eu.netherlands3d I should also see the package eu.netherlands3d.tiles3d in "My Registries".

What is actually happening?

It is not there. See reproduction steps.

Other relevant information

Unless I am seeing this incorrectly, I count 10 eu.netherlands3d packages in my listing. Because I can discover the package when I add that scope explicitly, I have a gut feeling that this is a pagination issue. Either the OpenUPM registry returns 10 results and does not offer pagination; or Unity UPM does not have pagination when it comes to Scoped Registries. I do not know whether this is actually the case, but it sounds a lot like it and I hope you know more about this and know of a fix?

@favoyang favoyang added the bug Something isn't working label Oct 23, 2023
@favoyang
Copy link
Member

It is definitely a bug for the search endpoint that UPM uses to detect packages for a given scope.

@favoyang
Copy link
Member

The issue has been resolved.

@mvriel
Copy link
Contributor Author

mvriel commented Oct 25, 2023

I can confirm that I can now see the packages that I was missing before! 🎉

@mvriel
Copy link
Contributor Author

mvriel commented Oct 25, 2023

Thanks for the quick fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants