Try our conversational search powered by Generative AI!
AI OnAI Off
Camel Case Config and Episerver Find UI Conflict
As my colleague's explanation, camel case is not supported by the UI. At leas these properties to be pascal case for th UI to work: Title, Url, Excerpt, MetaData, MeataData.BestBetPhrase.
The option we see is to somehow override the responses from EditorialBoostingController (/EPiServer/Find/api/editorialboosting/searchwithweights/) and change these properties back to pascal on the way.
As a theoretical example, this could be achieved by i.eg., creating a custom implementation of the EditorialBoostingController or a proxy that transforms requests from EditorialBoostingController, so that it only affects the boosting preview in UI.
I hope this helps.
Jul 14, 2017 5:24
Actully I fixed this by adding a custom json resolver which if the api was in a list or follow a certain pattern, the formater will be Default(which is paskal) otherwise it follow the global configuration.
Jul 14, 2017 7:16
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
Hi Everyone,
When I config application to serialize the json in camel case boosting page in find ui shows everything in undefined. if you trace the dGrid values, you can see all culumn definitions and asignments are in paskal case. so when you pass a camelCase json it result in undefined values.
I couldn't find any solution to config camel case serialization globally and fix this issue.