Skip to content

Adding @ref to request A, changes behaviour to request B that does not use @ref. #916

@Irench1k

Description

@Irench1k

If I update the data and store it in the @name variable, then requests that don’t use @ref variable will use the old data, while requests with @ref variable will use the new data.

  1. Send the initial request A that returns uuid "57c55f31-a26c-45bf-8794-3a71c2f5e08c”
  2. Both B (without @ref) and C (with @ref) reference expected value (which is the same value "57c55f31-a26c-45bf-8794-3a71c2f5e08c”)
Image
  1. Resend the request A again, which now gets a new uuid value “4385beb7-386d-40be-b3eb-8b880cb551be”
Image
  1. Now request B (without @ref) reference the previous data (equal to “ 57c55f31-a26c-45bf-8794-3a71c2f5e08c”)
Image
  1. But request C (with @ref) references the updated data (equal to “ 4385beb7-386d-40be-b3eb-8b880cb551be”)
Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions