fix: #1494 Port AdminButton from gatsby to next.js

[sonechca]

Issue This PR Addresses

Fixed: #1494

Type of Change

• Bugfix: Change which fixes an issue
• New Feature: Change which adds functionality
• Documentation Update: Change which improves documentation
• UI: Change which improves UI

Description

Checklist

• Quality: This PR builds and passes our npm test and works locally
• Tests: This PR includes thorough tests or an explanation of why it does not
• Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not (if applicable)
• Documentation: This PR includes updated/added documentation to user exposed functionality or configuration variables are added/changed or an explanation of why it does not(if applicable)

[tonyvugithub]

@sonechca : Hi there, we are in the process of reviewing these migrated to Next PRs. Just wonder if you are still interested to work on this as we would like you to make some changes to your PR. Please let us know in case you decided to drop this then we can assign the issue to others. Thank you.

[humphd]

A couple of things to do, and also, please git mv the file src/frontend/next/src/components/AdminButtons/AdminButtons.tsx to src/frontend/next/src/components/AdminButtons.tsx (i.e., get rid of the directory).

[humphd]

Delete this file.

[humphd]

Once #1521 lands (hopefully soon), we can change this to:

import { useUser } from '../UserProvider';

[humphd]

This can become:

const user = useUser();

[humphd]

Also, you need a rebase on master to pickup the package.json changes:

git checkout master
git pull upstream master
git checkout Port-AdminButtons
git rebase master
...fix conflicts...
git add src/frontend/next/package.json
git rebase --continue

[humphd]

@sonechca what's happening here? I'd like to get this shipped today.

[humphd]

We decided to move this to 1.6, and we'll take the work in #1504 to add a dummy AdminButtons component for now.

[yuanLeeMidori]

close by #1619