-
## Summary
Hi, as previously requested here: #832. Could this be reconsidered for implementation? Now that there is a AsyncDelegateCommand, it seems this would also be similarly useful. This increa…
-
### Is there an existing issue for this?
- [X] I have searched the existing open and closed issues
### Current Behavior
Prowlarr is running in a docker container, my containers are hosted using a m…
-
Hi,
Are you sure to register as singleton is a good way ?
In this case all clients will receive notification on their pages.
-
### Would you like to work on this feature?
None
### What problem are you trying to solve?
As far as I can tell, there's only a way to create new events which all get displayed separately -- I need…
-
### Is there an existing issue for this?
- [X] I have searched the existing open and closed issues
### Current Behavior
A number of sites aren't pulling new scenes that I can find on tpdb. Ot…
-
### Which Umbraco version are you using? (Please write the *exact* version, example: 10.1.0)
14.2.0
### Bug summary
When having over 500 members, editing and saving the default member type fails an…
nymwo updated
1 month ago
-
It would be really cool if these two items were merged. Currently if you fire an event on one the other doesn't know about it, and vice versa.
-
**Describe the bug**
When getting the picked Umbraco Commerce store on our homepage (datatype: Umbraco.Commerce.StorePicker) an error occurs.
Looks like the store ID is empty when getting the publis…
-
Making the aggregator extend EventEmitter means that you could, in theory, nest your aggregators.
In addition, it would present the opportunity to make it so that the aggregator emits events (rathe…
-
```
import { EventAggregator } from "aurelia-event-aggregator";
@inject(EventAggregator)
export class Index
{
constructor(eventAggregator)
{
this.eventAggregator = eventAggregator;
thi…