Hi Bubble community,
This past week, we had another one of our “hackathon days” (see this post and this post). To recap, these are days when the entire team focuses on smaller “qualify-of-life” features, as a break from our longer-running projects. As always, many of these ideas came from the community!
A number of these features have already rolled out, while others are getting the finishing touches (these will probably be rolled out on Monday, since we don’t want to launch too many new things on a Friday afternoon). Below is the list of features which are already deployed, and I’ll update this list as more get out:
-
For errors in the Debugger that have an error code and ask you to reach out to the Bubble team, there is a new link that will take you directly to the bug report form, with some fields pre-filled. @marca
-
The :extract operator on datetimes now lets you specify the time zone (static or dynamic) to use for the extraction. @cal
-
Date pickers now consistently have the option for “Time format”, which lets you switch between 24-hour time and AM/PM. @marca
-
In Settings > Languages, for the “Language field on the user type” feature, you can now select a field that’s an option set - and you can use the display or any attribute on that option set. @cal
-
You can now duplicate a custom view in the App Data tab. @jonah
-
Uploading data via CSV should now be able to handle numeric ranges. @cal
-
If your app uses the email confirmation action, you will see a new built-in field on User which lets you toggle whether the email address has been confirmed (you can only toggle this in a development version, e.g. for testing purposes). @zoe
-
When you see the ‘empty privacy rule’ warning in the property editor, it will now tell you which data type is missing the privacy rule, and clicking on it should more reliably take you to the Privacy subtab for that data type. @jonah
-
Similarly, if you are using the Bubble-built Box plugin, we have a new informative warning to set the Privacy rules for Box files. @miri
-
The Bubble-built Segment plugin now no longer asks for keys that we don’t use, and steps for obtaining the needed key are better documented. @miri
-
The “Manually enter API response” will now save the results of the previously saved Initialize if there is one, to give you a head start on manually entering your own. (To use: call “Initialize call”, save whatever field mapping, then go to “Manually enter API response” - you’'ll see the API response Bubble got from the “Initialize call”. If you “Initialize call” and save field mappings again, it will reset the manual entry field.) @sam8
-
(For plugin creators) There is now a versioning system for our plugin platform, meaning if we need to make breaking changes to the plugin platform, you will be able to stay on the old version of the platform until you are ready to upgrade, just like how you can with the Bubble app editor. (This feature will not be rolled out until the next time we need to release a breaking change for the plugin platform.) @cal
Edit: These features were rolled out after the initial post.
-
(8/24) There are some new animations available! These bring an element in/out from the left/right/up/down, but without a bounce. @aless
-
(8/24) For fixed cell repeating groups, previously we would always fill in every cell of each “page” - so if you had 12 items and pages with 5 slots, you would see #1-5 on page 1, #6-10 on page 2, and #8-12 on page 3. There is a new setting on fixed cell repeating groups, “Stable page offset”, that will allow the last page to be only partially full; among other things, this means that paginating back and forth will have consistent results on each page. @aless
-
(8/24) Much like how you could “Manually enter API response” for a JSON API call, you can now do so for XML API calls as well. @aless
-
(8/25) For collaborators on your app, there’s a new permission level for accessing the data of your app that lets the collaborator see the data, but not use “Run as”. @zoe
-
(8/25) The mapping of autocompleted geographic search results to actual geographic locations should be more accurate now (this was particularly evident when doing searches for non-full addresses, like “Alaska, USA”) (we apologize for all the Alaskans who thought they lived in Arizona). @remy
-
(8/26) There is a new data source, “Arbitrary datetime”, where you can type in a datetime as a string; we do our best to parse what you mean. @marca
-
(8/26) Database triggers will have a more descriptive entry in your Server Logs, so that they are easier to spot. @pete.vilter
This was truly a team effort - thanks also to @JeffT, @eve, @malcolm, @jess, @carla, @Jeremy, @ethanreeder, @heather, @erik.bubble, @DavidS, @vivienne, @alex.bolanos, @mpearlman, @theodor, @josh and @emmanuel for assisting in the QA effort!
Cheers,
Allen on behalf of the Bubble team
.
