1.12.1

What's Changed

• Fix/frontend bump version issues by @vitormarcal in #108

Full Changelog: v1.12.0...v1.12.1

1.12.0

BREAKING CHANGES:
app.email variables change to chatvault.email variables

What's Changed

• feat: fail fast when creating chatvault dirs fails by @vitormarcal in #104
• feat: enable delete chat by @vitormarcal in #107

Full Changelog: v1.11.1...v1.12.0

1.11.1

What's Changed

• log custom local datetitme pattern by @vitormarcal in #90
• upgrade nuxt to 3.8.2 by @vitormarcal in #92
• build: update gradle dependencies by @vitormarcal in #94
• Bump vite from 4.5.1 to 4.5.2 in /frontend by @dependabot in #96
• bump: upgrade to nuxt 3.9.3 by @vitormarcal in #102
• update README.md by @vitormarcal in #103

Full Changelog: v1.11.0...v1.11.1

1.11.0

What's Changed

• improve exception handler by @vitormarcal in #84
• fix failed tests by @vitormarcal in #86
• update README.md by @vitormarcal in #87
• (feature)frontend improve exception handle by @vitormarcal in #89

Full Changelog: v1.10.0...v1.11.0

1.10.0

TL;DR set chatvault.msgparser.dateformat even though it is currently optional for resolving message date formats

When you generate an export file via Whatsapp, the format may be different depending on your phone's language and locale settings and also depending on the language settings within the app. Therefore, it is quite difficult to infer a message date and on certain occasions it is impossible to resolve some ambiguities: 03/01/2023, how do you know what is the value of the day and what is the value of the month?

With this release the application has limited support for trying to infer the appropriate format taking as parameters other messages in the same import where there is no ambiguity. For example, if the application processed a date 12/15/2023, the application knows that 15 is a day because the months go up to the number 12.

If an import only has ambiguous dates, the import will fail.

You can help parse by placing a message with an unambiguous date on the first line of text in the file, but you can fix the date format of the message by setting the optional property chatvault.msgparser.dateformat to solve the problem once and for all.

It's actually recommended to set chatvault.msgparser.dateformat even though it's currently optional.

Check your output message file and put in the appropriate format.

Some examples of formats:
dd/MM/YYYY HH:mm to something like 25/06/2023 12:18
MM-dd-YY, HH:mm for something like 06/25/23, 12:18
dd/MM/YYYY hh:mm a to something like 06/25/2023 00:18 AM
and so on.

What's Changed

• 82 bugbackend message date with unexpected format prevents message import by @vitormarcal in #83

Full Changelog: v1.9.0...v1.10.0

1.9.0

What's Changed

• 77 feat:backend deduplicate messages when importing by @vitormarcal in #81

Full Changelog: v1.8.0...v1.9.0

v1.8.0

What's Changed

• 46 update group profile image by @vitormarcal in #70
• add icon to open or close the chat configuration by @vitormarcal in #79

Full Changelog: v1.7.0...v1.8.0

v1.7.0

What's Changed

• update README.md by @vitormarcal in #67
• 68 few refactorings by @vitormarcal in #69
• remove legacy chat importer by @vitormarcal in #75
• fix date format by @vitormarcal in #76

Full Changelog: v1.6.0...v1.7.0

v1.6.0

What's Changed

• 64 feat find all attachment messageid from gallery by @vitormarcal in #66

Full Changelog: v1.5.0...v1.6.0

v1.5.0

What's Changed

• 32 create a media gallery by @vitormarcal in #62

Full Changelog: v1.4.0...v1.5.0