github appsmithorg/appsmith v1.8.5
Release v1.8.5 🌈

latest releases: v1.25, v1.24.1, v1.24...
19 months ago

What's new?

Big release again. Lots of new features, some big ones coming soon, lots of improvements and bug fixes, too, but what we most want to talk about is, “Is templatize a word? If not, shouldn’t it be?” We mean, we have over a hundred templates planned, over half of them almost ready to meet you, and yet, somehow, spellchecks throw an error when we use it. We tried it below, so we know. If you agree, like this release. If you disagree, share it wide and let others participate in the debate.

🚀 Features

  • The Table gets a Select column type so you can, say, dynamically set Menus to offer preselected values as inputs. If that doesn’t make sense, here’s a use case but we’d love to see more from you. [#16337]
  • The Table has also offered several datatypes in column settings. Now, we also auto-detect the datatype if your first five rows are not empty and set those columns to the detected datatypes. Life’s good when you are on Appsmith. [#16701]
  • In even more Table super-powers, we now let you load a very large number of rows without performance issues. Try it and let us know how much you love it. 😍 [#16872]
  • Your end-users saw some empty space below the contents of your app. Sometimes, there was a scroll bar, too. “Why”, we asked. We didn’t find answers, so we changed that. Let us know if you know better and want that empty space back. [#16747]
  • For our Business edition users, if you invited a user with a role of your choice and expected the Role dropdown to go back to its default state, we have now met your expectations. You will have to wait just a tad longer for us to beat your expectations with Audit Logs and granular access controls. [#17259]

💪🏾 Improvements

  • In some situations, resizing the container for your widgets messed around with the widgets outside the container. We have now improved this experience. [#17243]
  • Remember forking templates into existing apps? Awesome feature, didn’t work with apps connected to your Git. It now does, thus making it even more awesome, but the awesomest bit is you can now import specific pages from a template without pesky errors blocking you. Go forth and templatize. [#17184]
  • Speaking of templates, they now show up right for your version of Appsmith and don’t need hacks to work on the version they are supposed to. Achieving that kind of fit is what makes us work through nights. [#16843]
  • JavaScript pros, did you use return statements with promises before and hated it? Don’t. Because you don’t have to anymore. [#16802]
  • Datatypes for MySQL have been mapped so prepared statements know the big difference between “null” and null or {{”172019”}}, our birthday, and {{172019}}, just a big number. [#17017]
  • Cursor-based pagination with GraphQL queries showed paginated responses when you ran the query on the Query screen. We thought, “Queries can live without that privilege”, so we changed that behavior to only let widgets like the Table call paginated results with an onPageChange trigger. [#17316]
  • Translating this 502-word PR for you, we now have a very smart method to avoid errors with the same name for a widget, a query, or a binding. [#17074]
  • We are smart with numbers. Mongo is literal. That conflict of natures led you to some trouble with Mongo regex.We are now less smart, more literal, so Mongo regex works. Happy? [#16977]
  • In line with ArangoDB’s decision to change their default database’s name to _system, the name of the default database in Appsmith will now be _system when a new ArangoDB datasource is created. Thanks, reachtokish, for this. [#16198]
  • The Dropdown doesn’t just look better and consistent with our new Design System’s guidelines; it has also stopped dropping unhappy surprises on you and works nicely with Google Sheets. [#16201], [#16718]
  • In more from Project Reskinning, we have 14 more widgets looking good and feeling stylish.
    • Map Charts have now been upgraded with new legend, captions, and font styles, follow the themes you select, and are spaced right. [#16921]
    • The Rich Text Editor, JSONForms, and Forms widgets now look like they belong with the other reskinned widgets. Videos just got trained with themes and look stylish with the new border properties. [#17355]
    • The Audio widget got some makeovers with consistent spacing, good font sizes, and weights. [#17295]
    • Speaking of Audio, this is a four-in-one PR and asks the Button, ButtonGroup, Menu Button, and Icon widgets to look nicer. [#17093]
    • This is a five-in-one and converts the Container, List, Modal, StatBox, and Tabs widgets to their better-looking versions. [#16974]
  • When signing with Google OAuth2 or GitHub OAuth into a self-hosted Appsmith instance on a proxy-enabled server, the access token request now goes through the proxy. [#17114]
  • Ever see the Evaluation and Binding Prompt panes get cropped when they appeared towards the bottom of the Property pane? We fixed that. [#17081]
  • In the same vein, we have also made some changes to the Property pane for all widgets, making it simpler for you to use props under Content and Style tabs. [#16639]
  • In your workspace’s General Settings, you can enter your website and e-mail. Those fields now flag non-standard entries and make sure you enter correctly formatted ones. [#16912]
  • Settings under APIs, Queries, and JS Objects all showed different UI components. We have turned them all into switches or toggles. Much better. [#16990]
  • This probably doesn’t deserve mention but we thought we should let you know Error pages everywhere in Appsmith show a bit more of our orange than before. [#17109]

🐛 Bug Fixes

  • Anyone can now leave a Business Edition workspace again. Sorry if you had to reach out to your workspace admin too many times just to get out. [#574]
  • Sometimes, when you asked the Table to go to the next page, it just didn’t. The Table, for all its super-powers, is very stubborn, but we trained it to behave better. [#17405]
  • The Select widget didn’t play well with numeric labels, leading to the widget crashing. We asked labels to play nice with numbers. Who doesn’t? [#17006]
  • If you have tried the new Slider widgets and set the default or minimum value to 0, you must have seen the placeholder text instead of the expected 0. Unknown to you and us, the Input and the Slider widgets were conspiring against both of us. We have now quashed the coup. [#17082]
  • The Code Scanner didn’t reset itself when you wanted it to. It now does. Simple. [#17185]
  • Dynamic bindings in GraphQL queries and mutations broke sometimes and they took autocomplete down with them. We fixed both in this one PR. We are calling this, “Two errors, one PR.” [#17229]
  • Now choosing No on being asked for confirmation to run an action leads to the right toast messages. We understand you mean, “No” when you say, “No.” [#17249]
  • When you added an API, you saw two key-value pair fields under Headers. If you went to another screen and came back to Headers you saw four new key-value pairs. This was not some multiplication magic. This was a bug. We quashed it. [#17052]
  • The Appsmith Debugger is a very useful feature but it became very lazy with JSON and RAW responses. We debugged the Debugger, made it very active, and also fixed some whitespace. The whitespace had nothing to do with its laziness, though, so if you think about it, “Two fixes, one PR” again. [#16971]
  • If you saw a blank screen for situations when you knew the app wasn’t loading certain chunks of JavaScript, we corrected that to a screen with a little orange and some very helpful error messages. If you didn’t see the blank screen ever, good. Very good. [#17168]
  • Frame ancestors, that old thing that lets you embed your apps securely, is now new and improved to work with values in ' ' without ignoring the single quotes. [#16983]
  • You can now . That’s all. [#17095]
  • Vertical alignment for the Table’s columns would stay persistent to the last setting used even when you wanted it to revert to its default. Same when you cleared any JavaScript in the prop and toggled JS off. Rebellious widgets are our favorite bugs to fix, so we got to this one quickly. We think they may not be your favorites, so we have buried this here. [#16733]
  • The Checkbox widget caught a reskinning bug and continued to show in red. We treated it, quashed the bug, and brought it back to gray, even when you aren’t hovering over it. [#17355]

🛡 Security

  • The iFrame widget now runs in a sandbox for all new Appsmith instances. New and existing instances can toggle the environment variable APPSMITH_DISABLE_IFRAME_WIDGET_SANDBOX =TRUE or =FALSE to disable or enable it respectively, but we recommend you keep it =FALSE. [#11426]
  • We have fixed a bug that inadvertently let you edit some other workspace on the same instance than the one you intended to. This didn’t affect anyone neither will it going forward. [#17266]

Don't miss a new appsmith release

NewReleases is sending notifications on new releases.