add support for Where().isIn query

[richard457]

Pull Request Summary

Feature: Add isIn Query Operator to Where

Overview

This PR introduces a new isIn operator to the Brick query system, allowing users to easily query for values that exist within a list (e.g., SQL IN clause). This is useful for filtering records where a field matches any value in a provided list.

Key Changes

• Compare Enum:

  • Added a new value: inList to represent the "IN" comparison.

• Where Class:

  • Added a new convenience method:

    Where isIn(List<dynamic> values)

    This allows queries like:

    Query(where: [Where('name').isIn(['Alice', 'Bob', 'Charlie'])])

• Unit Tests:

  • Added tests to where_test.dart to verify:
    • isIn works for integers:
      Where('id').isIn([1, 2, 3])
    • isIn works for strings:
      Where('name').isIn(['Alice', 'Bob'])

Usage Example

final query = Query(where: [Where('status').isIn(['pending', 'approved'])]);

[tshedor]

@richard457 there's a lot of added code here that isn't relevant to the PR. Can you please remove your changes to supabase_example?

[richard457]

@tshedor yes Done.

[tshedor]

@richard457 thank you for submitting this PR. It's a huge help for me.

This feature would be useful and I'd like to get it into Brick. I've got some small pieces of feedback inline. More broadly, could you please add unit tests for query_sql_transformer and query_supabase_transformer?

[richard457]

Thanks for the feedback @tshedor allow me to work on this on my earliest time.

[wwcom227]

@tshedor @richard457 Is there any new progress on this PR? This feature is really needed.

[richard457]

Sorry, I got a lot, I am working on to address your comment, allow me today to send a patch. @tshedor

[richard457]

@tshedor I uploaded changes, your review is highly needed, let me know if anything else I need to address will address it right way.

[tshedor]

@richard457 very close now

[richard457]

@tshedor I was wrong the error I was experiencing might not related, I took your suggestion thanks and sorry to take long.

[richard457]

@tshedor Please let me know if there is anything for me to address.

[richard457]

Committed change @tshedor ://

[tshedor]

@richard457 looks like there's just one failing test on supabase_provider_test and then this is good to go

[richard457]

cc @tshedor ://

[KiddoV]

Can we have new version for those updated packages in this commit?
Currently I have to use:

dependencies:
  brick_core: ^2.0.0 # <- Need new version
  brick_sqlite: ^4.1.0 # <- Need new version
  brick_supabase: ^2.0.0 # <- Need new version
  brick_offline_first: ^4.0.1
  brick_offline_first_with_supabase: ^2.1.0 # <- This one included the updated code, but other packages are not compatible 
  
dependency_overrides:
    brick_core:
    git:
      url: https://github.com/GetDutchie/brick.git
      ref: 01a6d98463c2be5a978259b2f3302db69664cada
      path: packages/brick_core
  brick_sqlite:
    git:
      url: https://github.com/GetDutchie/brick.git
      ref: 01a6d98463c2be5a978259b2f3302db69664cada
      path: packages/brick_sqlite
  brick_supabase:
    git:
      url: https://github.com/GetDutchie/brick.git
      ref: 01a6d98463c2be5a978259b2f3302db69664cada
      path: packages/brick_supabase

Thanks,