The HTML string was being converted to a local 8-bit string prior to parsing with tidy.

According to Qt documentation, this works on Unix systems as toLocal8Bit() is equivalent to toUtf8(), however, it may not on Windows, and may result in character replacement.

Gitlab: #1536
Change-Id: I7aec98cffbd9d72771d1c489f52b38dbb3a1ed9f

Change-Id: I8d5f968fbedbc884c91416246049a0ef4cd652eb

Andreas Traczyk authored 1 year ago and Sébastien Blin committed 1 year ago

Depend on tidy API for attribute extraction rather than regexes.

1. htmlparser methods return nodes instead of pre-parsed strings
2. htmlparser provides some methods to extract text/attr from nodes

Gitlab: #1248
Change-Id: I367d703680938fb0b7c5055ac41e079c1322da30

also separate debug and muteDaemon options so that "jami -dq" shows
debug informations from the client.

Change-Id: Ic69c5cf8b6a8ef4aa1fff607d01a541dab3e6da2

Andreas Traczyk authored 2 years ago and Sébastien Blin committed 1 year ago

Introduces MessageParser to encapsulate text treatment for raw text messages.

The async parsing sequence is as follows:
- Markdown -> HTML (md4c)
- link coloration (tidy-html5)
- notify UI
- request link preview info from PreviewEngine for the first link
- Preview engine uses QtNetwork instead of QtWebengine
- Linkification is handled by MessageParser instead of linkify.js

QtWebengine is no longer required for message parsing.

Gitlab: #1033
Gitlab: #855
Change-Id: Ief9b91aa291caf284f08230acaf57976f80fa05b

Several subsequent patches will be required so this can be used for our tests.

Gitlab: #899
Change-Id: I3939770ed34fe40aafa2ab93e2bab3cd77a20955

- simplifies and fixes the python build script for Windows
- applies pep8 to the script also

Gitlab: #899
Change-Id: Ieb3debd08ddf1649a46208fc52362d20c504c1b1

Change-Id: Idf38e82631a4e22540aa5dec8ec2db0ab4a38c2e

This is moved to libjami in commit e4fa507.
Also bump libjami to e4fa507.

Change-Id: I5414f0b4987aec6474c09d8ecc4d1675c565853d

The linker would throw errors starting with GCC 10 (see:
https://gcc.gnu.org/gcc-10/porting_to.html).  Final fix for
<#882>.

* tests/unittests/account_unittest.cpp (globalEnv): Remove variable.
* tests/unittests/contact_unittest.cpp: Likewise.

Change-Id: I08cff055590c06afb9423759ff3e2c6c6c790e94

Sébastien Blin authored 2 years ago and Andreas Traczyk committed 2 years ago

Change-Id: Ia6d7ba0ee9e32d5830b35b863b3981e2487df183
GitLab: #821

Sébastien Blin authored 2 years ago and Amin Bandali committed 2 years ago

Change-Id: Idc960c96e4647dbb6f8c1d64f545fe25c80bbaa5

Change-Id: I8eb66c1c3cddb3bf73b6784a9876dd9dc9c12481

Andreas Traczyk authored 3 years ago and Kateryna Kostiuk committed 3 years ago

+ Check early for Qt6 and remove module list duplication.
+ Add qrencode-win32 as a submodule. Remove unused libqrencode
  submodule(GNU/Linux and macOS use package dependencies).
+ Remove unused ReleaseCompile option.

REQUIRES adjustments to:
- https://jenkins.jami.net/view/clients/job/client-qt-msvc-tests
(JenkinsFile ??)

Gitlab: #601
Change-Id: Ied65c9aaead86009d70f68705f8592950dab2dfa

Ming Rui Zhang authored 3 years ago and Sébastien Blin committed 3 years ago

Remove unsupported QtQuick One component and it will be
added back in the following patches

Change-Id: Iad206a880096cf956a4220a81dca85a993721fbd

1. Move JAMI_DATA_HOME, JAMI_CONFIG_HOME, JAMI_CACHE_HOME
   setup into individual test main entry
2. Use google test assertion macros instead of Qt
3. Add QT_QPA_FONTDIR to avoid QFont warnings
4. Tests will now fail if the env variables cannot be set

Change-Id: I63f6498d26b646d8ebc60799d8797fd5f13b54f9

Using a custom getter setter cause the setting of the value to
require manual changed signal emission and in addition to being
error prone, this prevents the changed signal from being emitted
upon initial selection. Some excess workaround code may be removed
in following commits.

This patch also refactors the banned contact signaling as part of
an accountadapter connection cleanup.

Change-Id: I73fb751001e53e086adc7a6a8d706671c2878a77

1. Add building tests only option in the build script
2. Google test intergration enhancement
3. Properly use QSignalSpy wait function

Change-Id: I5ec1b33e191cebd8a14c19d92ee4eb4d40f054c3

Change-Id: I7e3db31838884bc585d981ced91b4294cd5a8c14

Maxim Cournoyer authored 3 years ago and Sébastien Blin committed 3 years ago

Automated via the following command:

  $ git grep -l dring | grep -v '.ts$' | xargs sed -i
  's/dring/jamid/g'
  $ git ls-files | xargs sed -i 's,bin/jamid.lib,bin/jami.lib,g'
  $ git ls-files | xargs sed -i 's,src/jamid,src/jami,g'
  $ git ls-files | xargs sed -i 's,-mutejamid,-mutejami,g'
  $ git checkout docker

Change-Id: I030209b60817372f866055daadb4d0a1c1e2e9df

Add global test environment for google test

Change-Id: Id035ebf31498e11574b6bf4671b4c6e12d29ddc7

Change-Id: I6ee537ee1ee3928c93b9a579e2b55b6ef97af779

Ming Rui Zhang authored 3 years ago and Sébastien Blin committed 3 years ago

- Also updated the INSTALL.md

Gitlab: #385

Change-Id: Ib5bf9f0348dbc6da57e586475d698fe8dec0351b

Albert Babí Oller authored 4 years ago and Andreas Traczyk committed 4 years ago

- add QtQuickTest, QtTest and googletest support
- create tests folder within cmake hierarchy
- avoid using wildcards in Dockerfile

Change-Id: I81661a86757f01333538908dbc81a0bafae00ab7