CardFilter.Visible - invalid value for filter

Hello,

looks like CardFilter.Visible is not a valid filter, at least now.

Open and All filters are working fine.

Trello reported an error: ‘invalid value for filter’

************** Texte de l’exception ************** System.Net.Http.HttpRequestException: Trello reported an error: ‘invalid value for filter’ at Manatee.Trello.Internal.ExceptionHandling.DebugLog.Error(Exception e, Boolean shouldThrow) in C:\Users\gregd\Desktop\Manatee.Trello\Manatee.Trello\Internal\ExceptionHandling\DebugLog.cs:line 26 at Manatee.Trello.Internal.DataAccess.JsonRepository.ValidateResponse(IRestRequest request) in C:\Users\gregd\Desktop\Manatee.Trello\Manatee.Trello\Internal\DataAccess\JsonRepository.cs:line 64 at Manatee.Trello.Internal.DataAccess.JsonRepository.Execute[T](TrelloAuthorization auth, Endpoint endpoint, IDictionary2 parameters) in C:\Users\gregd\Desktop\Manatee.Trello\Manatee.Trello\Internal\DataAccess\JsonRepository.cs:line 29 at Manatee.Trello.ReadOnlyCardCollection.Update() in C:\Users\gregd\Desktop\Manatee.Trello\Manatee.Trello\CardCollection.cs:line 64 at Manatee.Trello.ReadOnlyCollection1.GetEnumerator() in C:\Users\gregd\Desktop\Manatee.Trello\Manatee.Trello\ReadOnlyCollection.cs:line 59 at System.Linq.Enumerable.Count[TSource](IEnumerable1 source, Func2 predicate)

[gregsdennis]

From Trello support:

We support the filter filter=visible for cards only when it is a nested resource in specific other resources. For instance, the filter works if you are getting cards as a nested resource from the board object (/1/boards/{boardID}/cards?filter=visible). However, the list object is not one that supports that. I’m going to update our documentation to explicitly outline which objects do support that filter.

I believe that you could use filter=open instead and get the same expected outcome. Let me know if that doesn’t do the trick for you!

It seems odd to me that they’d support visible on boards but not lists. I’ll have to update to catch this special case.

[gregsdennis]

When I asked about the inconsistent behavior, they replied:

Unfortunately, I don’t have a good answer as to why we’ve ended up with inconsistent behavior. However, I’ve added this to our backlog and hopefully we’ll get it fixed sometime in the future. Going forward, we’ll likely lean into cards=open. Sorry for the confusion!