-
Notifications
You must be signed in to change notification settings - Fork 260
Open
Open
Enhancement
Copy link
Labels
Component: UIIssue needs changes to the user interfaceIssue needs changes to the user interfaceEffort: TrivialIssues require < 1 day of workIssues require < 1 day of workImpact: MediumIssue is impactful with a bad, or no, workaroundIssue is impactful with a bad, or no, workaroundUI: StringsIssues with the Strings widget or overall display of strings elsewhereIssues with the Strings widget or overall display of strings elsewhere
Description
What is the feature you'd like to have?
I'm digging through a blob of partially compressed, poorly obfuscated data, encoded as a hex string in a format which happens to exactly mirror how we escape invalid bytes in strings, which is making it very difficult to figure out what's going on.
There is nuance if you manually count the amount of backslashes, but I can very easily send you 50 examples where that is still ambiguous.
Emitting non ascii string members and other escapees with a differently colored Token would help make things much more clear
Are any alternative solutions acceptable?
Can't think of any others
Additional Information:
Please add any other context or screenshots that would help us understand your feature request here.
Metadata
Metadata
Assignees
Labels
Component: UIIssue needs changes to the user interfaceIssue needs changes to the user interfaceEffort: TrivialIssues require < 1 day of workIssues require < 1 day of workImpact: MediumIssue is impactful with a bad, or no, workaroundIssue is impactful with a bad, or no, workaroundUI: StringsIssues with the Strings widget or overall display of strings elsewhereIssues with the Strings widget or overall display of strings elsewhere