Seb

so before this went down, I made this pull request ```ts const E = 50; type E = "e"; type EEE = E; const EEEE = Array; const e =...

@manast If there was a way to specify how the process is spawned (command arguments?) then this problem would be easier to solve, at least with tsconfig-paths.

I'm having a similar issue. Trying to use a where clause with linked does not work in the same way: ```rust let users = users::Entity::find() .find_also_linked(UserRole) .filter(roles::Column::Name.eq("superuser")) .all(db) .await .map_err(ApiError::db)?;...

Here's how I did it in my project. ```rs /// Bridges an async [Loadable] with a synchronous [MediaSource]. struct LoadableMediaSource { rt: Handle, loadable: BoxedLoadable, } impl MediaSource for LoadableMediaSource...

Yeah at the moment there's not a way to do this from within pulseshitter itself. The config file is stored in `$XDG_CONFIG_HOME` or `$HOME/.config` with a ron file called `pulseshitter-config.ron`...

This has now been implemented in [v3.0.0](https://github.com/Enitoni/pulseshitter/releases/tag/v3.0.0)! You no longer have to find the config file and edit it manually.

Expanding on this, one thing that would help immensely with both restoring and managing current sources available is a consistent reliable way to filter out old sources (ones that are...

I'm also running into this issue and have not found a workaround. Manually editing the operation does not seem very efficient, so it would be nice if this was supported.

I'm having the same issue.

Yes! Please add this. I was just about to make an issue for this. This makes blocking have less friction and makes the UX much better, especially in terms of...