Use new types introduced in Nextcloud 21 and bump compatibility

[hlnd]

Signed-off-by: Ole Morten [email protected]

Fixes #165.

Changes proposed in this pull request:

• Use new types.
• Bump compatibility: I'm not intimately familiar with Nextcloud's APIs, but I suppose using this new class is going to break compatibility with Nextcloud <21.

[brknkfr]

Seems to work fine with a new nextcloud 21 installation.

[violoncelloCH]

Thanks for the PR @hlnd
@ChristophWurst could you take a look if those changes make sense and if there is nothing missing?
(That way I could hopefully create a new release next week after this is merged)

CI is failing because of #159 (which is already out of date again)

[almereyda]

After checking the patch, I think it might not be the best idea to change an existing migration.

On the other hand were the DBAL types removed with 21, and that migration couldn't possibly run anymore.

But will this patch also allow to take care of clients, which have existing users_external tables already initialized with Type::String, or is this kind of type migration taken care of by the NC21 upgrade migration?

[ChristophWurst]

The migration will still be run for new migrations. Existing migration files have to be touched.

[doobry-systemli]

I can verify that the app works as expected with Nextcloud 21.

Would be nice if this PR could be merged and a new app release be published @violoncelloCH 😊

[violoncelloCH]

thanks for the PR @hlnd !

[oriolo]

Well done, It works as expected.
Just two minor issues to report with this configuration:
'<imap_server>', , '<ssl/tls>', ', true, true
the user is created but no group is defined for him nor the email address.
Just in case I would also like to suggest to add a 7th parameter in which one can define the quota limit.
Thank you.

[ychaouche]

Thank you all. The red enable untested app has now disappeared from the admin pannel > apps.