Skip to content

[Bug]: REST queries imported from the Query Library cannot use application global variables. #2083

@itribs

Description

@itribs

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

In the Query Library, the “Run JavaScript” query can access the application context after being imported into an app. For example, return currentUser.email works correctly. However, for a “REST Query”, even though {{currentUser.email}} is set, it fails to retrieve the value after the app is imported.

Expected Behavior

The context that should be obtained, such as global variables.

Steps to reproduce

In the Query Library, create a “REST Query” with {{currentUser.email}} in its parameters. Then, create a “Run JavaScript” query with the code return currentUser.email.

After importing both queries into an application:

The “Run JavaScript” query correctly outputs the currentUser.email.
The “REST Query” fails to retrieve the value for currentUser.email.

Environment

docker image:all in one
system: debian 12

Additional Information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions