f9a90a6561
## Context <img width="1349" alt="Screenshot 2025-01-13 at 17 18 24" src="https://github.com/user-attachments/assets/4f5da0e9-0245-41c6-bde2-4d52e0ba34ed" /> Feature flags are stored in DB and then cast as FeatureFlag gql type from its corresponding enum. This means if a value from the DB does not match that enum type, the gql server will reject the call when returning the object in the resolver. (see screenshot above) To solve that, we want to do 2 things: - The ORM should still return the feature flag even if it's not valid, this is actually in the DB so we don't want to "hide" that, however we now have a warning message. - The service is not changed for the same reason, the limitation comes from gql behaviour so this is not the goal of the service nor the ORM to act on it (except the warning message) - The resolver should be updated, here we want to filter-out non-valid feature flags so it does not break the API. Because featureFlags used to be auto-generated by nestjsquery and we want to change its behavior, I had to manually create a resolveField for featureFlags and remove the auto-generated one. That means we lose some features such as filter/sort coming from nestjs-query pagination (which is something we will want to implement once we will remove nestjs-query but that's a whole other subject)
Run yarn dev while server running on port 3000