5 replies to this topic

[rhodges]

IResolverIgnoreRule

https://github.com/M...-Type-Discovery

 

Can anyone tell me if this has been removed, or moved to a different dll? Since the source closed up, I can't just go look for it myself anymore 

 

Edit: Decompiling things, it looks like it is gone?? And to top it off, you never fixed the bug where the auto upgrade turns itself back on, so now as soon as my Emby restarts, it'll upgrade and I'll have to fix it, turn it off and figure something else out?

 

Edit 2: All of your ignore logic is hard coded inside CoreResolutionIgnoreRule and that isn't even injected into LibraryManager? Seems like a step back in your design.

Edited by rhodges, 19 April 2019 - 02:36 PM.

[Luke]

I removed it to avoid having to loop over a list of rules for every single file. I didn't realize anyone was using this. What are you trying to accomplish?

[rhodges]

I used it to bring back the option to ignore hidden files.

 

A lot of anime use linked files for opening/closing credits. I don't want to remux things into a single file. I want to retain the original files, without any name changes, etc. At one point, you ignored them and life was good.

 

That was removed. We chatted about that a bit in a different thread and basically, that ability wasn't going to be added back. After I discovered that interface, I was happy and added it back for myself.

 

Now that interface is gone. It seems you are determined not to allow me to ignore hidden files 

[Luke]

If and only if it's not going to impact library can performance, then i can look at adding it back. thanks.

[rhodges]

I never had a problem with it. Of course, you/we will be at the mercy of plugin developers. If the list is empty, aka, no developer injected anything, then it shouldn't have any impact. But, if a nefarious/bad developer wanted to do something stupid inside it, then there will be a problem.

 

Feel free to optimize or adjust as needed. I'm just looking for a hook, with the path to the file that I can give you a yes/no to import it. Assume yes, first person who says no, exit (which is what was there if I am not mistaken).

[rhodges]

If and only if it's not going to impact library can performance, then i can look at adding it back. thanks.

Sorry to be a bother, but, is this something you're still considering adding back? Anything I can do to help? Or just be quiet and let you work?