MERL-1204: onLogout server action - app router

[matthewguywright]

Description

Created the onLogout server action for the app router.

Testing

To test this follow these steps:

1. Pull this branch
2. Run npm install
3. Navigate in the terminal to the examples/next/app-router folder
4. Setup the env.local and a local site for Faust. Be sure to set the frontend url in the Faust WP Plugin settings.
5. Add the following to the app-router/app/page.js file inside the main element:

     // import up top
     import { onLogout } from '@faustwp/experimental-app-router';

     // inside the <main> body element
      <form action={onLogout}>
        <button type="submit">Logout</button>
      </form>

6. Run npm install and then npm run build
7. Run npm run dev -w @faustwp/app-router-example
8. Navigate to your localhost:3000
9. You should see your homepage with a logout button
10. Add a cookie to your browser with dev tools called http://localhost:<yourLocalPortForLocalWPSite>-rt and give it any value
11. Click on logout, the cookie should be deleted

[github-actions]

📦 Next.js Bundle Analysis for @faustwp/getting-started-example

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[changeset-bot]

⚠️ No Changeset found

Latest commit: ac6930d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[TeresaGobble]

Hi @matthewguywright , Nice work on this! Thank you for your thorough testing instructions too, that's always appreciated! 😊

I'm not seeing the cookie get deleted upon clicking the logout button. See the video below:

Screen.Recording.2023-08-31.at.5.22.20.PM.mov

Am I adding the cookie as expected? If so, perhaps we can test it in my environment to make sure everything looks as it should.

[blakewilson]

Hey @TeresaGobble, it looks like you are setting a refresh token with your front ends site URL. In this case it should be your WP sites address:

http://localhost:<yourLocalPortForLocalWPSite>-rt

For instance, my local WordPress site is http://headless.local, so my cookie name would be:

http://headless.local-rt 

(I like your video demo! That's very useful)

[TeresaGobble]

Thank you so much @blakewilson! That was the issue. This works as intended. Nicely done Matt! 👍