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

Update actions.mdx #11112

Closed
wants to merge 1 commit into from
Closed

Update actions.mdx #11112

wants to merge 1 commit into from

Conversation

vladstudio
Copy link

There's an error on line 157 - the object needs to be spread.

Description (required)

Related issues & labels (optional)

  • Closes #
  • Suggested label:

There's an error on line 157 - the object needs to be spread.
@astrobot-houston
Copy link
Contributor

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File Note
en/guides/actions.mdx Source changed, localizations will be marked as outdated.
Warnings reference
Icon Description
🔄️ The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Copy link

netlify bot commented Mar 1, 2025

Deploy Preview for astro-docs-2 ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 202a7d0
🔍 Latest deploy log https://app.netlify.com/sites/astro-docs-2/deploys/67c294737edd2600086b4b9c
😎 Deploy Preview https://deploy-preview-11112--astro-docs-2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@ArmandPhilippot
Copy link
Member

Hi, and thanks for taking the time to fix the docs! However, I'm not sure this change is correct.
If we use the spread syntax, what is below the code snippet will be wrong since the user key will no longer exist:

Now, all of your user actions are callable from the actions.user object:

*    actions.user.getUser()
*    actions.user.createUser()

When you say there is an error, are you sure you are using actions.user.getUser() and not actions.getUser()?

@vladstudio
Copy link
Author

Oh oops! I was not careful enough indeed, and was trying to access actions.getUser(). Sorry for the confusion, and thanks for catching.

@vladstudio vladstudio closed this Mar 1, 2025
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

Successfully merging this pull request may close these issues.

3 participants