double brackets problem still i Revo??

I worked with Evo a lot before and one of biggest broblem I found was double brackets used in snippets. It makes many troubles with JS code generated by snippets. I know that I can str_replace ’[[’ to ’[ [’ in outputted $data but I still can’t do it with some Curl data (I don’t know yet why, some data are generated correctly, some not). I think OK, it is time to upgrade to Revolution. But I’m very suprised, in Revo it is still double bracked as snippet TAG. Why? Why after years of development other TAG is not used, it was knonw issue a long time ago...

Quote from: peter222 at Dec 10, 2010, 01:55 AM

I worked with Evo a lot before and one of biggest broblem I found was double brackets used in snippets. It makes many troubles with JS code generated by snippets. I know that I can str_replace ’[[’ to ’[ [’ in outputted $data but I still can’t do it with some Curl data (I don’t know yet why, some data are generated correctly, some not). I think OK, it is time to upgrade to Revolution. But I’m very suprised, in Revo it is still double bracked as snippet TAG. Why? Why after years of development other TAG is not used, it was knonw issue a long time ago...

There are going to be collisions with whatever tag characters we adopt. That said, the parser can be called manually in the API with any tag prefix and suffix you want, which means you can use a custom tag when processing problematic data. We’re certainly open to suggestions for improvement though, e.g. perhaps in the future the entire core parser can be configured with a custom tag prefix and suffix.

Yes but for somethink like ^#...#^ or ^~...~^ would be less problematic than [[...]] which is commonly used with JSON data I think.

you can use a custom tag when processing problematic data

Where Can I read how to do it? Maybe is any workaround for my problem?

In other words, is any other way to workaround problem witch JSON data displaying than str_replace ’[[’ to ’[ [’? I still can’t find solution, my data generated by Curl is correctly displayed out of Modx, but Modx corrupt it.