Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building computed properties around the queue #323

Open
natotthomer opened this issue Mar 11, 2020 · 0 comments
Open

Building computed properties around the queue #323

natotthomer opened this issue Mar 11, 2020 · 0 comments

Comments

@natotthomer
Copy link

natotthomer commented Mar 11, 2020

I'm working on a project where, for a number of reasons, I'd like to know how many messages are currently in the flash messages service. I'd use those to compute some properties and control application state. But I cannot figure out how to accurately listen for changes to the queue. If my application.js injects the service as flashMessages, I was thinking I'd be able to do something like:

hasFlashMessages: Ember.computed('flashMessages.queue', function....

or

hasFlashMessages: Ember.computed('flashMessages.queue.@each', function....

or

hasFlashMessages: Ember.computed('flashMessages.queue.[]', function....

or something to that effect. None of these work. What has worked is doing it at a granular level in the corresponding HBS files:

{{#if (and flashMessages.queue flashMessages.queue.length))}}
...
{{/if}}

Furthermore, when I try to use the Handlebars log helper, I get some strange results:

{{log flashMessages.queue}} --> only logs once on initial render and never again, regardless of number of messages in the queue
{{log flashMessages.queue.length}} --> consistently logs each time the queue grows and shrinks.

I'm fine with my workaround for now, but I'd love to have slightly more control over this as my application grows in complexity.

Is there something I'm missing? Something I could do to start building computed properties around the number of messages in the flash service? This aside, we love the package! It's been extremely useful for us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant