Remove GraphQL / GitHub / Keystone links in production

[Achisingh]

The keystone Admin UI popover button that consisted of Keystone links to API Explorer, GitHub Repository and Keystone Documentation, present at the top of the left side-bar is replaced with only the Sign out button in production mode after authentication.

[changeset-bot]

🦋 Changeset detected

Latest commit: 4c7b471

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 15 packages

Name	Type
@keystone-6/core	Minor
@keystone-6/auth	Major
@keystone-6/cloudinary	Major
@keystone-6/fields-document	Major
@keystone-6/session-store-redis	Major
@keystone-6/example-auth	Patch
@keystone-6/examples-app-basic	Patch
@keystone-6/example-ecommerce	Patch
@keystone-6/example-graphql-api-endpoint	Patch
@keystone-6/example-roles	Patch
@keystone-6/example-sandbox	Patch
@keystone-6/example-testing	Patch
@keystone-6/example-with-auth	Patch
@keystone-6/website	Patch
@keystone-6/example-document-field	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
keystone-next-docs	✅ Ready (Inspect)	Visit Preview	May 23, 2022 at 5:16AM (UTC)

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[Achisingh]

Hi @raveling
This is what the UI looks after replacing the popover button with Sign-out in production. As you will see the text is coming very close to the button. Any suggestions on how to go about this?

For reference, this is how the text and the popover button are in dev mode.

[Achisingh]

This is how the Signed in as looks like after stylus update

[raveling]

That's acceptable from a Design point of view. Thanks @Achisingh !

Missed something

[emmatown]

Could you update the test at

keystone/tests/examples-smoke-tests/basic.test.ts

Lines 14 to 20 in fd8d4a6

	test('sign out and sign in', async () => {
	await page.click('[aria-label="Links and signout"]');
	await Promise.all([page.waitForNavigation(), page.click('button:has-text("Sign out")')]);
	await page.fill('[placeholder="email"]', 'admin@keystonejs.com');
	await page.fill('[placeholder="password"]', 'password');
	await Promise.all([page.waitForNavigation(), page.click('button:has-text("Sign In")')]);
	});

? The test will need to do different behavior depending on whether it's running the prod vs dev mode. You'll probably want to pass the mode variable to

keystone/tests/examples-smoke-tests/utils.ts

Line 154 in fd8d4a6

tests(playwright[browserName]);

[Achisingh]

Could you update the test at

keystone/tests/examples-smoke-tests/basic.test.ts

Lines 14 to 20 in fd8d4a6

	test('sign out and sign in', async () => {
	await page.click('[aria-label="Links and signout"]');
	await Promise.all([page.waitForNavigation(), page.click('button:has-text("Sign out")')]);
	await page.fill('[placeholder="email"]', 'admin@keystonejs.com');
	await page.fill('[placeholder="password"]', 'password');
	await Promise.all([page.waitForNavigation(), page.click('button:has-text("Sign In")')]);
	});

? The test will need to do different behavior depending on whether it's running the prod vs dev mode. You'll probably want to pass the mode variable to

keystone/tests/examples-smoke-tests/utils.ts

Line 154 in fd8d4a6

tests(playwright[browserName]);

Done. Refer to:
https://github.com/keystonejs/keystone/pull/7546/commits/4c7b4713526280a6c1ded38c3308813300cb1442