Ben Hollis
Ben Hollis
This would be to add a new column or columns to Columns.tsx for: 1. Whether an item is harmonizable. 2. What its deepsight level is.
I could've sworn we already had this. This would be a new column in the Organizer (Columns.tsx) that would display the armor's intrinsic perk (e.g. Sonar Amplifier).
There are a number of bugs or at least weird corner cases with how item movement works. I'd love for us to fix them, but the item movement logic is...
In https://github.com/DestinyItemManager/DIM/pull/10068 I said: > An alternative I was thinking about was to use a lockfile strategy, leveraging [node-proper-lockfile](https://github.com/moxystudio/node-proper-lockfile) - this has the advantage of not requiring the pre-cache step...
I'm not sure how much this is related to the recent changes to how we prevent scroll chaining, if at all, but I can frequently get into a situation where...
This adds the ability to set an in-game identifier (name, color, icon) for a DIM loadout, with the intention that it's used as the default when copying the loadout to...
It'd be nice to see the full rendered preview of ornaments.
This is interesting - this loadout doesn't say "better stats available", but there is a set with the same values for all included stats *and* more points in ignored stats....
I'd like to replace our `observeStore` function with a "listener middleware" inspired by https://github.com/reduxjs/redux-toolkit/blob/0678c2e195a70c34cd26bddbfd29043bc36d1362/packages/toolkit/src/listenerMiddleware/index.ts#L427 This would allow us to break an import chain between code that uses observeStore and all...
It should be possible to treat these as another plug set? I'm not sure if that's the best way to do it, or if it should wait for #8097