directly returning a `use`d resource should still be reactive #958

NullVoxPopuli · 2023-07-25T03:16:37Z

For example:

const Clock = resource(({ use }) => {
  return use(Time({ intervalMs: 1000 });
});

…ediately-return-used-resources Resolves #958

NullVoxPopuli closed this as completed in 77d54e6 Jul 26, 2023

NullVoxPopuli added a commit that referenced this issue Jul 26, 2023

Merge pull request #960 from NullVoxPopuli/provide-the-ability-to-imm…

3f19818

…ediately-return-used-resources Resolves #958

github-actions bot mentioned this issue Jul 26, 2023

Release Preview #962

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

directly returning a `use`d resource should still be reactive #958

directly returning a `use`d resource should still be reactive #958

NullVoxPopuli commented Jul 25, 2023

directly returning a used resource should still be reactive #958

directly returning a used resource should still be reactive #958

Comments

NullVoxPopuli commented Jul 25, 2023

directly returning a `use`d resource should still be reactive #958

directly returning a `use`d resource should still be reactive #958