crowdstrike / ember-resource-tasks Goto Github PK

Question for maintainers: myself, @vitch @HeroicEric,

the purpose of this library was mainly to:

• provide a method by which to use derived data patterns with the safety of ember-concurrency tasks
• provide a way to access the same invocation/value/data across components without each component having to compute that same data across each of those components.

ember-resources already provides a useTask and will soon (wip here) have a shared utility that will do this for us, with an api that may end up like:

import Component from '@glimmer/component';
import { useTask, shared } from 'ember-resources';

export default class MyComponent extends Component {
   // reactive & derived ember-concurrency task
   // this could also just be _any_ resource
  compute = useTask(this, ...);
  
  // as long as only `data` is accessed (instead of `compute`), the value of `compute` will be shared among
  // all instances of MyComponent.
  //
  // this, like the current MemoizedTask, is still the same as instead defining this on a service 
  // and accessing that service from the component,
  // except: you don't need to define a service.
  // 
  data = shared(this, () => this.compute); 
}  

This issue provides visibility into Renovate updates and their statuses. Learn more

Open

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

• chore(deps): update type definitions (@types/ember, @types/ember-resolver, @types/ember__application, @types/ember__array, @types/ember__component, @types/ember__controller, @types/ember__debug, @types/ember__destroyable, @types/ember__engine, @types/ember__error, @types/ember__object, @types/ember__polyfills, @types/ember__routing, @types/ember__runloop, @types/ember__service, @types/ember__template, @types/ember__test, @types/ember__test-helpers, @types/ember__utils, @types/qunit)
• chore(deps): update lint dependencies (@typescript-eslint/eslint-plugin, @typescript-eslint/parser, ember-template-lint, eslint, eslint-config-prettier, eslint-plugin-decorator-position, eslint-plugin-ember, eslint-plugin-prettier, eslint-plugin-qunit, prettier)
• chore(deps): update cli dependencies (major) (ember-auto-import, ember-cli)
• chore(deps): update framework dependencies (major) (ember-maybe-import-regenerator, ember-source)
• chore(deps): update lint dependencies (major) (@commitlint/cli, @commitlint/config-conventional, @typescript-eslint/eslint-plugin, @typescript-eslint/parser, ember-template-lint, eslint, eslint-plugin-decorator-position, eslint-plugin-markdown, eslint-plugin-prettier, eslint-plugin-qunit, remark-cli, remark-lint, remark-preset-lint-recommended)
• chore(deps): update semantic-release monorepo (major) (@semantic-release/changelog, @semantic-release/git, semantic-release)
• chore(deps): update type definitions (major) (@types/ember, @types/ember-qunit, @types/ember__application, @types/ember__array, @types/ember__component, @types/ember__controller, @types/ember__debug, @types/ember__destroyable, @types/ember__engine, @types/ember__error, @types/ember__object, @types/ember__polyfills, @types/ember__routing, @types/ember__runloop, @types/ember__service, @types/ember__template, @types/ember__test, @types/ember__utils, @types/htmlbars-inline-precompile)
• Click on this checkbox to rebase all open PRs at once

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

Why is there an extra object under the named key? Seems like extra boilerplate. Is there a use case I'm not seeing?

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀