Dan Gebhardt
Dan Gebhardt
This was intentionally left out initially, as it's unclear how errors should flow from the adapter, and back through the store and model in ember-data.js. Validations have been added to...
Currently, validations are handled in forms by bootstrap. This isn't very robust - model-level validations would be better.
This could be useful for scenarios in which two different addons export an identically named component or helper, which should be used independently in consuming addons / engines. As with...
This list of ignored addons was carried over from ember-cli-dependency-lint: https://github.com/dgeb/ember-cli-addon-guard/blob/master/lib/utils/discover-addon-versions.js#L59-L67 However, since ember-cli-addon-guard checks whether addons have "run-time" contents, it's probably safe to remove this list. The tradeoff is...
After ember-cli-legacy-helpers is removed from ember-cli, we should plan to support plain `component` and `helper` blueprints here (since they won't conflict with the legacy blueprints).
From #28 > This is a short-term compromise for fixing the current spew of output. We include only `.d.ts` files and `package.json` files from `node_modules` in the input tree to...
I closed #22 because it was a bit of a premature optimization. Without benchmarking, it will not be readily apparent the best strategy to use for typing the specifiers used...
In a `Registry`, both factories and instances can be registered via `register`, unregistered via `unregister`, and accessed via `registration`. @krisselden and I discussed the benefits of separating the interfaces to...