Popup-Editor - After Save, JSON-String is corrupted
Solved
Hey there,
I have a big Problem with editing "JSON-Strings" (normal string / stringified JSON)
if I modify a value with a double click I can see my beauty formated JSON-Strings, nice...
but if I modify a small part and klick "save" my JSON is corrupted (Uncaught SyntaxError: Unexpected token in JSON at position ...)
example
before:
pure: "{\n\t\"node\":\"LINE1\\rLINE2\"\n}"
nice formated shown inside editor like:
{ "node":"LINE1 LINE2" }after save:
"{\n\t\"node\":\"LINE1\nLINE2\"\n}"
in short: my \\r gets a \n
thanks!
Greetings
crazyx13th
Thank you for your feedback.
We have worked out a new build to resolve this issue, please download and give it a try. Suppose you are using the windows system.
http://s3.mongobooster.com/download/releasesv6/nosqlbooster4mongo-6.2.10-beta.1.exe
Thank you for your feedback.
We have worked out a new build to resolve this issue, please download and give it a try. Suppose you are using the windows system.
http://s3.mongobooster.com/download/releasesv6/nosqlbooster4mongo-6.2.10-beta.1.exe
First view ist very good! Seem to work, but give me some time for real Practice (I had to revert a dump today...)
Thanks!!
First view ist very good! Seem to work, but give me some time for real Practice (I had to revert a dump today...)
Thanks!!
And yeah, win10-x64 :-)
And yeah, win10-x64 :-)
mhh.... working only if a \\r exists :-(
working:
not working
after edititing inside the "double-click-pupup" I got
sorry
thx!
mhh.... working only if a \\r exists :-(
working:
not working
after edititing inside the "double-click-pupup" I got
sorry
thx!
I tried again, and there was no error in the data store, but the display looked different when editing.
Because / r is a unique line wrap in the windows system, we have done some special treatment for / r. To put it simply, when / r exists, / n retains the original characters for editing.
When / r is not found, / n is interpreted as a newline character.
I tried again, and there was no error in the data store, but the display looked different when editing.
Because / r is a unique line wrap in the windows system, we have done some special treatment for / r. To put it simply, when / r exists, / n retains the original characters for editing.
When / r is not found, / n is interpreted as a newline character.
Hey, thanks for answering.
ok, but this is not the solution, because you MODIFY the original data (a "\\n" gets a "\n" after OPENING edit-popup). I give you a step by step example:
- insert:
- overview:
- edit document
All seems to be ok!
- now, I click edit to open the edit-popup
- after opening i click save (I did nothing / no manual editing!)
- overview shows the same as before:
BUT if I edit the document ...
"\\n" not there, only "\n"
thanks for your support! Hope you will fix this bug! :-)
Hey, thanks for answering.
ok, but this is not the solution, because you MODIFY the original data (a "\\n" gets a "\n" after OPENING edit-popup). I give you a step by step example:
- insert:
- overview:
- edit document
All seems to be ok!
- now, I click edit to open the edit-popup
- after opening i click save (I did nothing / no manual editing!)
- overview shows the same as before:
BUT if I edit the document ...
"\\n" not there, only "\n"
thanks for your support! Hope you will fix this bug! :-)
my example before:
this means after your current beta change if a "\\r" apears somewhere all gets fine... a "\\n" is a "\\n" after save
BUT
The Probleme is at OPENING the popup window he losing one "\"
what I sayed before: a "\\n" gets a "\n"
thanks!
my example before:
this means after your current beta change if a "\\r" apears somewhere all gets fine... a "\\n" is a "\\n" after save
BUT
The Probleme is at OPENING the popup window he losing one "\"
what I sayed before: a "\\n" gets a "\n"
thanks!
Thank you for your feedback. This problem is really a little more complicated than I thought, and there are still some problems with the text editor's handling of special characters. We have worked out a new test build to try to resolve this issue, please download and give it a try.
http://s3.mongobooster.com/download/releasesv6/nosqlbooster4mongo-6.2.10-beta.2.exe
BTW, you can also use the "edit document" meu item to edit the raw value.
Thank you for your feedback. This problem is really a little more complicated than I thought, and there are still some problems with the text editor's handling of special characters. We have worked out a new test build to try to resolve this issue, please download and give it a try.
http://s3.mongobooster.com/download/releasesv6/nosqlbooster4mongo-6.2.10-beta.2.exe
BTW, you can also use the "edit document" meu item to edit the raw value.
beta.2 looks perfect! I testet it with 10 huge json-strings (10x ~20k chars)
I will keep an Eye on this (compare before and after the next time), but for now I think you can "close" it.
thanks!!!
"BTW, you can also use the "edit document" meu item to edit the raw value."
yeah, I wrote that in my text :-)
but 10k-50k long json strings are better readable inside the popup-editor ;-)
beta.2 looks perfect! I testet it with 10 huge json-strings (10x ~20k chars)
I will keep an Eye on this (compare before and after the next time), but for now I think you can "close" it.
thanks!!!
"BTW, you can also use the "edit document" meu item to edit the raw value."
yeah, I wrote that in my text :-)
but 10k-50k long json strings are better readable inside the popup-editor ;-)
thx again for quick support,
fyi: since today I'm a "NoSQLBooster for MongoDB Personal License With 3 Years Software Assurance" User!
:-)
thx again for quick support,
fyi: since today I'm a "NoSQLBooster for MongoDB Personal License With 3 Years Software Assurance" User!
:-)
Replies have been locked on this page!