Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backport 1.16] fix: Invoke context() function with a list containing a custom context #861

Merged
merged 4 commits into from
May 31, 2024

Commits on May 30, 2024

  1. refactor: Use new test API with result matcher

    Merge test class with the new style from version 1.17.
    saig0 committed May 30, 2024
    Configuration menu
    Copy the full SHA
    4d9f341 View commit details
    Browse the repository at this point in the history
  2. test: Invoke context() with custom context

    (cherry picked from commit 1f896e7)
    saig0 committed May 30, 2024
    Configuration menu
    Copy the full SHA
    61da568 View commit details
    Browse the repository at this point in the history
  3. refactor: Reuse custom context helper

    (cherry picked from commit f3e7370)
    saig0 committed May 30, 2024
    Configuration menu
    Copy the full SHA
    0f95480 View commit details
    Browse the repository at this point in the history
  4. fix: Invoke context() with custom context

    The context function expects a list argument with context entries that contain a key and a value. The function checks that the key value is a string. To support a custom context value, the value must be resolved via value-mapper first before checking the type. Otherwise, the value may be not a FEEL Val type but something else.
    
    (cherry picked from commit 2416531)
    saig0 committed May 30, 2024
    Configuration menu
    Copy the full SHA
    3e5bc99 View commit details
    Browse the repository at this point in the history