Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Unanswered
← Having trouble viewing a widget

Hi Todd!

Is this a server-side rendered extension or a client-side rendered extension?

With a server side rendered extension I would expect to see entrypoint urls like these for Main and a secondary entrypoint based off the python route setup:

"url": "./sdk/authenticated/{featureName}",
"url": "./sdk/authenticated/{featureName}/hyc",

With a client side rendered extension using hash routing I would expect something like these:

"url": "{BASE_URL}/index.html",
"url": "{BASE_URL}/index.html#/hyc",

Without seeing the code, this looks like a little bit of a mixture of both.

Posted 3 years ago
0

Yes, this was the issue. I'm not sure how I messed it up but I created it as a CSR extension instead of a SSR extension. As a result there were no assets to build which is why I kept getting the 404. Once I fixed it to be SSR everything started working.

— Todd Culbertson   3 years ago
31 Views
0 Answers
3 years ago
3 years ago