Sanitize key in Developer Tools display

[tarunkishore2303]

Summary

Added an utility function to sanitize the string before displaying it in tree

Finishes #28984

How did you test this change?

Added test cases for the utility function that has been created.

[facebook-github-bot]

Hi @tarunkishore2303!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[kassens]

Not sure devtools should just modify and display something different. That seems like it could easily be confusing - especially when that small difference is the cause of some sort of bug and need debugging.

Not sure if this is a common issue as I don't work on devtools, maybe it could display invisible characters such as newline escape codes like JSON, i.e. \n?

@hoxyq

[hoxyq]

Not sure devtools should just modify and display something different. That seems like it could easily be confusing - especially when that small difference is the cause of some sort of bug and need debugging.

Not sure if this is a common issue as I don't work on devtools, maybe it could display invisible characters such as newline escape codes like JSON, i.e. \n?

@hoxyq

Yup, I think we don't need to replace anything here and instead use pre tag?
@tarunkishore2303 Could you please try wrapping the key text in pre tag and sharing a screenshot of how it looks?

I could help with building the extension locally, if needed.

[tarunkishore2303]

Yeah sure, I could do that. But I would need your help building the extension locally to test it out @hoxyq