You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did not inspect the code yet, but I think it would be great to mention at least in which order the calls are returned. Is it random, or first is last call, first is first call?
If it's random, could we establish additional parameters, something like:
sort/order="lifo" or "fifo" (just a quick idea, kbr knows better solutions I am sure)
limit=10 (optional)
Background: if someone just wants to check the last 10 calls, it is currently not clear if that would work with this libary module. Maybe it's just enough to extend the explanation in the documentation how to do so? Maybe it is already ordered in some way, but that should be written explicitely on top I guess.
The text was updated successfully, but these errors were encountered:
get_calls() returns the calls just in the order provided by the router. At time of writing it is the most recent call first.
The returned calls are instances of the class Call. So i.e. it's possible to inspect the attribute 'date' (which is of type datetime) or sort the list of calls by some attributes according to the needs.
The parameter 'num' corresponds to your suggestion of 'limit'.
Hi, I found in the documentation with URL:
https://fritzconnection.readthedocs.io/en/1.3.4/sources/library.html#module-fritzconnection.lib.fritzcall
this:
I did not inspect the code yet, but I think it would be great to mention at least in which order the calls are returned. Is it random, or first is last call, first is first call?
If it's random, could we establish additional parameters, something like:
Background: if someone just wants to check the last 10 calls, it is currently not clear if that would work with this libary module. Maybe it's just enough to extend the explanation in the documentation how to do so? Maybe it is already ordered in some way, but that should be written explicitely on top I guess.
The text was updated successfully, but these errors were encountered: