Ability to manually remove single class cache entry

[inossidabile]

Sometimes within specs it might be useful to substitute particular controller class. However Rails caches its instance if it was already queried before. So the trick won't work. Currently it's only possible to clear up all the cache at once. Let's add tiny method that allows deletion of particular key. It might be useful for other ClassCache users too as well.

[senny]

Can you post a the use-case, which uses the new method?

[inossidabile]

At WashOut specs I need to substitute WSDL serving controller. I do that using remove_const method. However Rails cache it's instance inside Reference. I don't want to clear it completely cause I know exact class that did change but I don't have straight API to do that.

Here's what I do atm:

https://github.com/inossidabile/wash_out/blob/master/spec/spec_helper.rb#L43

Since we already have a way to purge the cache completely why not give ability to purge it partially?

[senny]

I was curious to see how it's being used. As you can see the class ClassCache has no documentation. I think it is an internal class, which should not be accessed directly. To put it differently. This code can could change because we decide to refactor stuff. That's why I'm hesitant to add methods not used by the framework itself but targeting the user.

This is just my opinion though, let's wait what @carlosantoniodasilva @rafaelfranca have to say.

[inossidabile]

@senny I understand that for sure. However the absence of documentation and code privacy status doesn't make my task disappear 💃. If I get it right – there are no public ways to affect internal constantization cache. But it is required from time to time.

[senny]

I just wanted to express that if adding this new method is as brittle as the solution you already have (because it might break on refactorings). I'm in favor of your current solution even if it is a hack (you could also monkey-patch the delete method in).

[JonRowe]

Was wether this should be merged ever resolved @senny?

[pixeltrix]

@JonRowe no, this is definitely not something that should be merged - ClassCache is an internal implementation detail and there are much better ways to do what the original reporter needs.

[inossidabile]

@pixeltrix like what for instance?

[pixeltrix]

Create a mock API controller and use that, e.g. washout :mock_api