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

TUTORIAL: useResource now has a task #1151

Merged
merged 3 commits into from Nov 20, 2022
Merged

Conversation

jmmon
Copy link
Contributor

@jmmon jmmon commented Aug 26, 2022

What is it?

  • [ x ] Docs / tests

Description

I expected there to be a task for this tutorial but the given code was the same as the given solution, leaving nothing for users to do on this task. Now, users have two tasks:

  1. create the useResource$() function (there is an exact answer already provided in the text on the left to make it easy)
  2. create the component (I left the onResolved callback function in a comment, so all they need to do is lay out the component and props, like the example in the text on the left)

Use cases and why

    1. Provide a task for users for this tutorial
    1. Provide an opportunity for people to use the described function/component

Checklist:

  • [ x ] My code follows the developer guidelines of this project
  • [ x ] I have performed a self-review of my own code
  • [ n/a ] I have made corresponding changes to the documentation
  • [ n/a ] Added new tests to cover the fix / functionality

I expected there to be a task for this tutorial but the given code was the same as the given solution, leaving nothing for users to do on this task.
Now, users have two tasks:
1. create the `useResource$()` function (there is an exact answer already provided in the text on the left to make it easy)
2. create the <Resource> component (I left the `onResolved` callback function in a comment, so all they need to do is lay out the component and props like the example in the text on the left)
@mhevery
Copy link
Contributor

mhevery commented Aug 27, 2022

LGTM, please fix lint errors.

@gitguardian
Copy link

gitguardian bot commented Nov 19, 2022

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id Secret Commit Filename
- Google API Key ade2c3e packages/docs/scripts/showcase.js View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

@manucorporat manucorporat merged commit a0a52ca into QwikDev:main Nov 20, 2022
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.

None yet

3 participants