Feedback from Tekton: So the first issue I notice when using the @builder.io/react and @builder.io/react/lite packages is that the Builder class is simply exported without new type definitions or specific React bindings. What I would expect to see...
Targeting on an integer isn't supported. The only work around is to use the string type and wrap the integer in quotes. Additional points for allowing the use of less and greater than, for example, `accountAgeInYears > 3`
With the Typeform App, we would be able to embed Typeforms directly into Builder pages, aiding lead gen capture efforts. Types of forms: Engagement polls Entertaining quizzes Feedback surveys Order forms Application forms Branding questionnaire Re...
Customizing the body would be incredibly useful as some POST body has different schemas. example: body: { person: true, characteristics: { eyes: brown, hair: bald, weight: 180, } }
Hide Builder-generated console errors/warnings in all or just production environments
Sometimes Builder can generate a decent number of warnings in the console, depending on how your page is set up. It would be nice to have a flag in the SDK that can hide console warnings/errors production environments
From customer: I am trying to add a slug field for content type models, but right now the only option that really works for this is the “text” field type. Unfortunately, text fields on content models do not allow any real validation (outside of “r...
When publishing, giving the user the ability to add a note to say what changes have been made (like a commit message) to easily see what changes someone made during a publish. ex. changed url from /test to /test1
Currently you can support standard non typed versions of defineProps, such as defineProps(['prop1', 'prop2']) <-- supported in builder sdk in typescript, you would define them as defineProps<{ prop1: string, prop2: number }>() <-- not ...
0
