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
All Ash.Query modifications - select, sort, limit, offset, build and so on - are usual methods. Except one, the most used - filter - it is a macro. So it needs a require statement to be used. Which is a little bit annoying when you want to add a simple filter and only once in a file... I just go for build(filter:) combo in that case.
Would be convenient to have non-macro variant of filter exposed (which is do_filter). Maybe under name where?
In small discussion on Discord the following proposal was made: add where in Ash 3.1 (because there are too many things already in Ash 3 and it is too late to change filter to non-macro method even though it is desirable) and make it a primary way to add filters to queries in docs, then in Ash 4 deprecate filter.
The text was updated successfully, but these errors were encountered:
All
Ash.Query
modifications -select
,sort
,limit
,offset
,build
and so on - are usual methods. Except one, the most used -filter
- it is a macro. So it needs a require statement to be used. Which is a little bit annoying when you want to add a simple filter and only once in a file... I just go forbuild(filter:)
combo in that case.Would be convenient to have non-macro variant of
filter
exposed (which isdo_filter
). Maybe under namewhere
?In small discussion on Discord the following proposal was made: add
where
in Ash 3.1 (because there are too many things already in Ash 3 and it is too late to changefilter
to non-macro method even though it is desirable) and make it a primary way to add filters to queries in docs, then in Ash 4 deprecatefilter
.The text was updated successfully, but these errors were encountered: