Filip Kis

I had the same problem which occurred when I tried to render a second component. Few hours of debugging later I realised that the problem was not related to having...

Are you not missing `this.globalLogout.start()` somewhere to start the synchronisation.

It's definitely redundant data (but for our case we're OK with it). Here is a use case: Our app has comments and each comment has an author. The API returns...

If philosophy is of concern, we could make this into another function so it's not a `resovleIdentifier`, but something like `findInCache` or something like that.

> I'd rather store them as frozen fields, and maintain your own lookup map But they're more than frozen fields. We have some views on them and even some actions...

OK, I guess I'm not going to convince you to nudge here (and get the benefit of already existing cache and functions that need just slight modification vs. implementing my...

I'm having a similar issue (same User appearing in various arrays) except I'm not using references, but just `resolveIdentifier`. However, I just need to resolve it to get the user...

@10000multiplier and @Navipro70 no it won't that's the whole point of identifier.

[Bootstrap 5 is now released](https://blog.getbootstrap.com/2021/05/05/bootstrap-5/). Any ETA on when support could be expected?

A bit of debugging showed that the reason is that during `onAdd` method the `ng-sortable` will the dragged item from the list _and_ call the [`$scope.apply()`](https://github.com/SortableJS/angular-legacy-sortablejs/blob/36efdec0e3502b4f256972b6aa337414d28a2ba8/angular-legacy-sortable.js#L178) which will trigger the...