Merging configuration. about purify HOT 1 CLOSED

Hi @ljjackson,

At the moment the package forces the developer to publish the configuration file to change the Cache.SerializerPath from the vendor folder the storage folder.

This isn't entirely true - there's no issue using the default vendor folder (vendor/ezyang/HTMLPurifier). It may actually be ideal, since anytime you update HTMLPurifier, the cache is automatically flushed (since the whole folder will be replaced).

This is only an issue if your application has issues writing to that folder, in which case you should publish the config file to change the cache location.

This is the default for the underlying HTMLPurifier package - so I don't believe this needs to be changed, especially since it's super easy to simply publish the config file and have full visibility on where you want the cache stored.

from purify.