invalidate cache by key

What did I do:

@cache.invalidate("foo:client_id:{client_id}", args_map={"client_id": "client_id"})
async def bar(self, client_id):
    ...

What do I expect:

It works ! =)

What do I receive:

File ".../python3.9/site-packages/cashews/validation.py", line 40, in _wrap
    backend.delete_match(target.format({k: str(v) if v is not None else "" for k, v in _args.items()}))
KeyError: 'client_id'

What do I suggest:

backend.delete_match(target.format(**{k: str(v) if v is not None else "" for k, v in _args.items()}))

[AIGeneratedUsername]

@MasterGroosha Decorating is overkill in your example. Just call delete_match.

KEY_PREFIX: str = "simple"

@app.get("/invalidate/{number}")
async def invalidate_cache(number: int):
    await cache.delete_match(f"{KEY_PREFIX}:{number}")

If you still really want to decorate something, then perhaps read https://github.com/tiangolo/fastapi/issues/2662 and https://github.com/tiangolo/fastapi/issues/1743

Your question rather belongs to discussions, than to issues.

[Krukov]

@MasterGroosha Thanks for reporting

Yes the order order of decoration matter - and it is not an issue of cashews. It is related how decorators works, and how frameworks registers handler functions.

About args_map - in you case you should reverse you map:

@cache.invalidate("simple:{num}", args_map={"num": "number"})

But more right way is just use right variable in key

@cache.invalidate("simple:{number}")

args_map - is a solution when you don’t want to use the key directly

@cache(ttl="9999d")
async def simple_cached_function(num: int) -> int:
    return num
    
....
@app.get("/invalidate/{number}")
@cache.invalidate(simple_cached_function, args_map={"num": "number"})
async def invalidate_cache(number: int):
    return {"message": f"Invalidated {number}"}