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

Get more than 10 namespaces in the editor. #2

Closed
xnyl opened this issue Jul 2, 2018 · 5 comments
Closed

Get more than 10 namespaces in the editor. #2

xnyl opened this issue Jul 2, 2018 · 5 comments

Comments

@xnyl
Copy link

xnyl commented Jul 2, 2018

In our project we have few dozens of namespaces, like you mentioned in the docs:

We recommend you to create multiple smaller namespaces'.

However I can't access them in the editor and in the app. It seems that you allow only 10 namespaces and I can't see any pagination to navigate to 'hidden' ones. Is this intentional, or am I missing something? We are subscribed to paid plan.

@jamuhl
Copy link
Contributor

jamuhl commented Jul 2, 2018

Hi Tomasz, what you mean by limit of 10 namespaces - there is no limit.

screen shot 2018-07-02 at 18 49 57

screen shot 2018-07-02 at 18 50 20

Does that look different in your browser (we're using chrome on the screenshots provided)

@xnyl
Copy link
Author

xnyl commented Jul 2, 2018

Hi Jan,

You can see from the 1st screenshot that there is 'TickerStats' namespace which is not listed on any of theese lists. However I can access it by url. When I download namespaces using locize-cli, I have proper 18 namespaces. I'm using Chrome on Linux.

screenshot from 2018-07-02 19-02-44
screenshot from 2018-07-02 19-03-31

@jamuhl
Copy link
Contributor

jamuhl commented Jul 2, 2018

Should be fixed now...not sure what caused that - but we will dig deeper into it and check if there is something wrong in calculation of that.

@xnyl
Copy link
Author

xnyl commented Jul 3, 2018

Ok. Confirmed that it works now. Thank you. Btw really great job with this service! :-)

@xnyl xnyl closed this as completed Jul 3, 2018
@jamuhl
Copy link
Contributor

jamuhl commented Jul 3, 2018

We investigated deeper and indeed found a race condition which could lead to this - already applied a patch so hopefully won't happen again. Great to hear you like locize. If there is anything else - let me know - you also can directly reach us via support@locize.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants