Spaces are getting replaced in workflow inputs

harry6561 commented 10 months ago

Describe the Bug with repro steps

The latest version of standard logic app changes the space in message input body with some other characters.

Here is sample input message - EU-231K-00LI-RSVR-01.PV; 2023/9/22 2:0:4; 0

There are spaces in the date time format.

But if this input is passed to an HTTP action it removes the space from the message body.

This is the expected behavior.

If we do control + f, and search for space, it should show the spaces in message body as well.

What type of Logic App Is this happening in?

Standard (Portal)

Are you using new designer or old designer

New Designer

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

No response

Screenshots or Videos

No response

Browser

All browsers

Additional context

No response

AB#25386698

AB#25415822

AB#25539336

Eric-B-Wu commented 10 months ago

Hi @harry6561 thanks for reporting this issue. I tried reproducing your issue, but didn't seem to have the same issue - when looking at the input for my HTTP body action on a flow run, it seemed to still be able to see the white space. What I think may be happening is that the sample input message you are using: "EU-231K-00LI-RSVR-01.PV; 2023/9/22 2:0:4; 0" might not be using a space, but rather a different character that may look like a space. If you try copying the space from your input (where the space is not working) and paste it to a unicode identifier site ex. https://www.babelstone.co.uk/Unicode/whatisit.html, you'll be able to see what character is being for your input

harry6561 commented 10 months ago

@Eric-B-Wu : Thanks for the update. My input message has no-break space.

But it was detected as space in logic app before. It still works fine in runtime version - 4.25.2.21138

It seems to have changed from runtime - 4.26.1.21286. Currently it is not recognized as a space. Please let me know if you need more details.

Eric-B-Wu commented 10 months ago

In which case, let me transfer you to the backend, as they handle what happens at runtime, and they can follow up if anything changed there or if this was an intended

Eric-B-Wu commented 10 months ago

discussed with Jaydeep (backend engineer) seems like backend is actually returning whatever frontend passes - what's happening is that there are 2 different types of spaces being sent, when searching globally edge will filter all spaces to be the same, and thus why it may have been showing that the space existed there before. On the other hand, Monaco Editor (the place where we render the outputs) also has a search function. When search a space on there, it matches the unicode character instead of all spaces, so its why you wouldn't see that space. I've verified that this is not a regression, and this was always happening. Therefore, I'll mark it as a feature request, once an engineer on our team gets freed up, they can take a look at what's needed here