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`
Allow in-query case-insensitivity sorting option w/ Content API
Origin: Adam Innes 50000feet.com Clients concern is performance having to iterate over each pagination of 100 results and then sort. Currently: builder.getAll returns data and the output is: ["AB", "Aa"] when the desired output is ["Aa", "AB"] Exa...
Currently there are options to link/unlink and sync content in bulk. This ability doesn't exist for models. We just started using builder.io and we already have 3 environments and 15+ models and growing. Performing this action manually one-by-one ...
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...
Origin: https://forum.builder.io/t/case-insensitive-sort/3624 Clients concern is having to iterate over each pagination of 100 results and then sort. Goal: Allow user to designate case insensitivity in-query. Currently: builder.getAll returns data...
Query filters are great, but let's be honest, if someone builds the user facing functionality, it usually means the search bar need to be as "smart" as possible. Having the ability to filter the content in a fuzzy way would imo add a lot of value
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