Skip to content

issues Search Results · repo:glimmerjs/glimmer-di language:TypeScript

Filter by

15 results
 (68 ms)

15 results

inglimmerjs/glimmer-di (press backspace or delete to remove)

glimmerjs/glimmer-di
Deserializing absolute paths should not requires a type

For example deserializeSpecifier( /some-namespace/ ) currently returns type === /some-namespace/ . The leading / should be enough to inform the parser we are providing the path part of the specifier string ...
  • mixonic
  • Opened 
    on Nov 24, 2017
  • #45

glimmerjs/glimmer-di
Concept of service/access to container in Glimmer application?

Hey, great job with the library! I love the Ember CLI, TypeScript and Glimmer! However, I ve got a question for you - is is possible to somehow do service: Ember.inject.service() like in Ember? You write ...
  • e00dan
  • 3
  • Opened 
    on Jun 17, 2017
  • #44

glimmerjs/glimmer-di
Registry vs Resolver priority

The readme says the container in this example has both a registry and a resolver. The container will look for classes in both, but the registry always takes precedence. If the registry is empty, the container ...
  • ef4
  • 6
  • Opened 
    on Apr 14, 2017
  • #43

glimmerjs/glimmer-di
prod builds produce source maps, but then uglify discards them

We should likely not build \w maps if we discard them. Or we should build them, and not discard them.
  • stefanpenner
  • 1
  • Opened 
    on Apr 5, 2017
  • #42

glimmerjs/glimmer-di
Proposal: lookupAll(type)

Really excited to find this library (h/t @knownasilya) I d love to use this in Denali, but I d need one additional method on the container: a lookupAll(type) method. It would allow a consumer to lookup ...
  • davewasmer
  • Opened 
    on Mar 11, 2017
  • #32

glimmerjs/glimmer-di
Factories lack documentation

Regarding the new factoryFor method and it s response.
  • knownasilya
  • Opened 
    on Mar 11, 2017
  • #31

glimmerjs/glimmer-di
Babel error

I m getting the following error when attempting to use this lib: /Users/iradchenko/sandbox/core/node_modules/@glimmer/di/dist/commonjs/es5/registry.js:13 (0, _babelHelpers.classCallCheck)(this, ...
  • knownasilya
  • 11
  • Opened 
    on Feb 22, 2017
  • #27

glimmerjs/glimmer-di
Proposal: Automatically create backing JS component

Given a component with a template, it s assumed that there s a backing JS component. Would be nice if one was created automatically if it didn t exist. Besides being nice for ergonomics, would reduce code ...
  • asakusuma
  • 2
  • Opened 
    on Feb 17, 2017
  • #25

glimmerjs/glimmer-di
Proposal: Use opaque specifiers

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 to cache and access factories ...
  • dgeb
  • 2
  • Opened 
    on Feb 16, 2017
  • #24

glimmerjs/glimmer-di
Proposal: Remove registration options entirely

Currently there are two registration options: export interface RegistrationOptions { singleton?: boolean; instantiate?: boolean; } If we move ahead with https://github.com/glimmerjs/glimmer-di/issues/21 ...
  • dgeb
  • 3
  • Opened 
    on Feb 15, 2017
  • #23
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue search results · GitHub