-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Update tests for custom admin path #4375
base: master
Are you sure you want to change the base?
Conversation
@IgorKhromov. I pulled in your changes and it does not resolve the issue. Looks like there is still something hardcoded somewhere. |
Anyone else have insight on the custom admin path not working in beta-5? |
Any movement planned for this one? |
I think the small problem with your fix is:
your script-line: if (pathname !== `/${Keystone.adminPath}/${currentList.id}`) return; is wrong, because result has "double-slash" if (pathname !== `//test123/${currentList.id}`) return; thx! solution:(sould work,... I hope) if (pathname !== `${Keystone.adminPath}/${currentList.id}`) return; (not testet) const pathname = `${Keystone.adminPath}/${currentList.id}`; |
This branch has conflicts that must be resolved Could anyone fix this conflicts files to have pulled this fix ? pushing node_modules is not recommended =/ |
Thanks for flagging @dev-dem. It looks like the code fix was already merged to master in #4586, but tests were not updated as per this PR. Changes will be included in the next Keystone release. Regards, |
@stennie, thank you for the fast answer ! Best! |
FYI, a code fix for this issue is included in Keystone This PR is still open pending review of the changes for tests. Regards, |
Now with 'admin path' options, list loading is infinity and broken, because of hardcoded keystone path in query params sagas.