Kim Gustyr
Kim Gustyr
> Even if we do the above, this would: > For self-hosted lead to unexpected results if a self-hosted instance had a different set of flags or. For SaaS revert...
@kyle-ssg I've added: - Fetch mocks, as discussed in Slack. - Tests to ensure proper `getFlags` behaviour. - A test to ensure that the client preserves transient traits correctly.
Rewrote the implementation keeping existing interfaces intact and adding support for the `evaluationContext: EvaluationContext` configuration entry.
As discussed offline, added transiency support to `identify`, `setTrait` and `setTraits` interfaces.
Hello Thiago. Sorry to hear about an incident. Can you elaborate on the exact issue you encountered? If possible, can you share your `HorizontalPodAutoscaler` manifest and Helm values file so...
Contrary to the discussion here, I believe we should benefit from adding proper datetime support to the engine.
@dtrabanca Thanks for the suggestion! We'll look into solving this and will happily review any PRs. Opened a more general https://github.com/Flagsmith/flagsmith-charts/issues/278.
@matthewelwell Good catches Matt — I've updated the ECS task and fixed the docs (they weren't correct in the first place)
@chrfwow updated the issue with more details. We expect to open a PR for this soon as it's a critical customer concern.
> Additionally added a pre-commit hook to write version without having to build. Nice! That will likely be retired once we close #321, though.