Filter Node Doesn't support output generated assets #147

Currently the filter node, will only filter if the asset is actually registered in the data base, for example, if I wanted to generate a couple of procedural materials from incoming textures and then use keyword/regex to split those materials into multiple pipelines (outputs) the node won't register these materials, it seems to have to do with limitations in checking the extension of the incoming asset (it's only relying on it being in the asset database).

thank you.