I think the search/filter syntax as implemented on receptor would work better for the --filter option in sycli than the current requirement for json input.
I'd be happy to implement if you think its a good direction
syntax description
You can search for torrents using the search box at the top of the page. By default, it will search through torrent titles. You can also search other properties of torrents with propertyoperatorvalue, where operator is one of the following:
: matches values that contain value
== matches values that are equal to value
!= matches values that are not equal to value
> matches values that are greater than value
>= matches values that are greater than or equal to value
< matches values that are less than value
<= matches values that are less than or equal to value
I think the search/filter syntax as implemented on receptor would work better for the
--filter
option in sycli than the current requirement for json input.I'd be happy to implement if you think its a good direction
syntax description
You can search for torrents using the search box at the top of the page. By default, it will search through torrent titles. You can also search other properties of torrents with
propertyoperatorvalue
, whereoperator
is one of the following::
matches values that contain value==
matches values that are equal to value!=
matches values that are not equal to value>
matches values that are greater than value>=
matches values that are greater than or equal to value<
matches values that are less than value<=
matches values that are less than or equal to valueThe following torrent properties are searchable:
name
: torrent namepath
: download pathstatus
: paused | pending | leeching | idle | seeding | hashing | errorsize
: size in bytesprogress
: progress from 0 to 1priority
: 1-5, low to highavailability
: how much is available from the swarm, 0 to 1rate_up
: rate up in bits/secrate_down
: rate down in bits/secthrottle_up
: throttle up in bits/secthrottle_down
: throttle down in bits/sectransferred_up
: total transfer up in bits/sectransferred_down
: total transfer down in bits/sectracker
: tracker urlpeers
: number of peerstrackers
: number of trackersfiles
: number of filesHere are some example searches: