ricokahler / next-data-hooks Goto Github PK

It should be possible to attach more than just one datahook I believe. But I get an error. Can just one DataHook be delivered to getStaticProps()?

export const getStaticProps: GetStaticProps = async (context) => {
  const dataHooksProps = await getDataHooksProps({
    context,
    dataHooks: ParagraphExample.dataHooks,
  });

  const dataHooksProps2 = await getDataHooksProps({
    context,
    dataHooks: BlogPost.dataHooks,
  });

  

  return {
    props: { ...dataHooksProps, dataHooksProps2 },
  };

I also tried:
dataHooks: [ParagraphExample.dataHooks, BlogPost.dataHooks].

Even though the peerDependencies now include NextJS 12, a new package hasn't been released on npm yet. Thanks!

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update typescript-eslint monorepo to v8.2.0 (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency @types/react to v18.3.4
• chore(deps): update babel monorepo to v7.25.4 (@babel/plugin-transform-runtime, @babel/preset-env)
• chore(deps): update nextjs monorepo to v13.5.6 (create-next-app, next)
• chore(deps): update all (major) (@rollup/plugin-babel, @rollup/plugin-node-resolve, actions/checkout, actions/setup-node, codecov/codecov-action, prettier, react-error-boundary, rollup, typescript)
• chore(deps): update dependency eslint to v9
• chore(deps): update dependency jest to v29
• chore(deps): update nextjs monorepo to v14 (major) (create-next-app, next)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Component.dataHooks always is an array of the data hooks from other components and the createDataHook function.

similarly getStaticProps, unless extra static props are desired, is also the same every time you write it: calling getDataHooksProps.

couldn't both of these be generated by the babel plugin? from my little experience from using babel, this shouldn't be too tricky to make, and it would reduce a lot of extra code that is copied from page to page, and eliminates the chance of missing a step.

the only issue here would be how to know weather to use getStaticProps or getServerSideProps, since you can't tell that from the hook usage themselves.

i'd like to try to implement this, maybe as an optional thing you need to enable. what are your thoughts?

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Is this a known issue? I followed the tutorial and have no idea why this occurrs. Any ideas? Should I provide a github repo?

Great project! Tried to use it with my project, however, it was failing with an error Error: Could not find NextDataHooksContext. Ensure NextDataHooksProvider is configured correctly.

Tried to debug and ended up cloning the repo and running the example. First run, works (next 10.0.1), then proceeded to update Next to 10.1.3 (latest). Hit the exception

Thanks for the lib.
I wanted to implement this feature but had been confronted with 2 mature issues, that let me stick to simple function in the comp file, that will be called in a static function within a page.

1. The useHooks do not carry payloads… this is important to handle specific calls for specific instances of the same component in the same page.

2. The hook body is more like a static independent function without context… or index. This makes it hard to bind the data two the components if there are more than just one.
   Are there any plans to modify or add payload features in the future ?