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
 
Answered
Ideal frontend framework to be used with Q2's Jinja CSR?

Hi folks!

This is more of a curiousity question rather than serious or help-seeking question. I'm trying to get the know the Q2's ecosystem and would like to know what framework on frontend we all typically use here for extensions.

1.What framework/library you guys use for interactivity/reactivity on frontend? Why?

  1. I've used https://alpinejs.dev before and would like to know if anyone here used alpine.js for q2's CSR extensions? I think alpine.js would be a great framework to be used with Q2's jinja html pages. Any thoughts on this? https://github.com/vuejs/petite-vue would be a great alternative. https://aurelia.io/docs could be good- but I do think that might be really overkill. I think I'll go with AlpineJS here since its really lightweight and requires no building tool.

  2. Angular, React, Eleventy, NextJS, Remix, SolidJS, etc doesn't seem like a good fit for Q2's jinja html pages because those frameworks/library can't really be embedded into jinja html pages seamlessly without some serious NPM tooling, is this assumption fair? If not, what's your counter argument?

Posted 4 years ago
Votes Newest

Answers


Anyone that has built a CSR extension probably can give their valuable experience here. The idea with CSR is to use a frontend framework of your choice and then call back to your CSR extension via tecton.requestExtensionData.

  1. The Q2 SDK team has extensively documented the React framework and I have seen many extensions use React. It is evident that the team is very familiar with React. There is a first class guide on it with proper support. See the example at https://gitlab.com/Q2Antilles/sdk-examples/sdk-tecton-examples/-/tree/master/React

  2. Using something like Alpine is definitely possible. There may be some challenges with it. Namely integrating Tecton into Alpine might be a challenge. It should work though.

  3. Because Client Side Rendered extensions built with react doesn't use jinja there isn't really an issue. Having first class guide support is just hard to pass up.

Regardless, I would recommend using 2.115.0 or newer on SDK versions there are a lot of quality of life improvements that happened in that version that will make things easier.

Posted 4 years ago
Trey Teter
124 × 2 Administrator
139 Views
1 Answer
4 years ago
4 years ago
Tags