I know, you may have some intriguing questions about how things are done or exist in Bubble.
Well, hereās a question that most people may not have asked themselves yet.
Why is the field labeled āCreated Dateā (created by Bubble itself in any new data type) when used in expressions actually referred to as āCreation Dateā?
Iām sure some of you have caught yourself using the wrong label to sort a list when using this field, right!?
ć ¤
Whatās the intriguing thing about Bubble that you always wonder about while working on your projects?
Whyā¦
Things? (instead of item maybe?)
Make change to (instead of update)
And all of theses plugins that should be native stuff (API connector, multidropdown, RTEā¦)
This has annoyed me for so many years, and not just because of wanting to see things to be grammatically correct so that they are more easily understood, but because it actively makes it more difficult to know what to use for things like a PATCH API call. Do we structure the field as created_by or creation_dateā¦and from my recollection, neither work, and Bubble support never provided me the answer.
Does anybody know which way we label that field for a PATCH api call to work?
Other things that annoy be about incorrect grammar are things that indicate completed versus in progress, especially around āpage is loadedā event, which for me, the āedā portion of the verb load, indicates completeness, as in done in the past, however, the actual action is āwhen page is loadingā or āpage load initiatedā.
Why is āpage is fully loadedā the only condition that defaults to yes? Basically āwhen page is fully loaded is yesā is equal to āwhen page is fully loadedā
Fun fact, if you install the Bubble App Connector plugin and reference your own app on it, you can call backend workflows and access the return value as if it were a call from an API Connector.
