Another month, another round of improvements to Dromo! Here's what's new and updated:
Gorgeous error filtering
The review screen now sports a new UX for filtering errors, either across all rows or only in specific columns. Give it a spin in our demo here.
Dromo goes global
Seeing as we now have customers on six continents and users around the world, it was time to up our language support. Dromo can now be run natively in over 30 languages, including Czech, Malay, and Icelandic. All you need to do is pass a locale
setting.
A complete list of i18n options is in the docs.
Schema-based column matching
You can now opt for your users to match columns based on the fields in your schema, rather than the columns in their file. This can be useful when a file has a lot of irrelevant columns, or when you want the matching screen to look consistent across all your users.
Full details are here.
More customization options
In v2, we've expanded the options for overriding the default styling of the importer. Want to match the border radius of the modal to suit the look-and-feel of the rest of your app? No problem. Want to change the header weight to match your brand? Easy.
Read about all the options here.
Adding and removing rows programatically
Every row in a import is now assigned a unique identifier, which can be referenced in a row hook. This enables you to add or delete a row from within a step hook without trying to manage index positions.
Check out the new instance methods addRows and removeRows.
Bugs squashed 🐛
- We resolved an issue where
initialData
was ignored whenmanualInputOnly
was set to true. - We added an error message at the bottom of the column matching screen to alert the user to duplicate matches.
- We improved the default mapping behavior of the
required_with
validator.