Manuel

Could it be that issue https://github.com/parse-community/parse-dashboard/pull/2737#pullrequestreview-2797839917 still exists?

Superseded by https://github.com/parse-community/parse-dashboard/pull/2878

Fixed with recent dependency upgrades

> Ideally, we should extend Parse.File to simply be initialized without attempting to encode/decode the data specified by the uri. > 3. Attempt to save Parse.File and set to Parse.Object...

You want to save a Parse File with an external URL, without actually storing the file data in the Parse Server's storage? In other words, the file would point to...

To summarize: you create a Parse.File (for example from JSON) that points to a file that already exists in the Parse Server managed storage, and then save the Parse.File as...

This will require a rebase because of conflicts. Would you want to open a new PR just with `npm i -E [email protected]`, or whatever the latest version is?

> I can see following solution sensible: when info panel receives a click - remove selection in data browser. Not good, as now the cursor keys can be used to...

Closed via https://github.com/parse-community/parse-dashboard/pull/2871

You mean to convert `\n` to ``? Did you try to do that conversion on your data side? It may get escaped, but worth a try.