Skip to content

Adjust notifier to Nextcloud 17 #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
skjnldsv merged 4 commits into from
Jan 27, 2020
Merged

Adjust notifier to Nextcloud 17 #10

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
1bcac9d
Adjust notifier to Nextcloud 17
nickvergessen Jul 16, 2019
c258f66
Update info.xml
skjnldsv Jul 28, 2019
d5a5e49
Fix max version
skjnldsv Aug 23, 2019
3f8c786
Merge branch 'master' into bugfix/noid/notification-adjustments
skjnldsv Jan 27, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update info.xml
  • Loading branch information
@skjnldsv
skjnldsv authored Jul 28, 2019
commit c258f6611b736470b2a8432e88731ac510f63d26
8 changes: 4 additions & 4 deletions appinfo/info.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,14 +12,14 @@
<category>files</category>
<bugs>https://github.com/nextcloud/preferred_providers</bugs>
<dependencies>
<nextcloud min-version="14" max-version="17"/>
<nextcloud min-version="17" max-version="18"/>
Copy link
Member Author

@nickvergessen nickvergessen Aug 19, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claiming to be compatible with a version that is not even started yet? did you misunderstand the max-version? Or what's the reason behind it? if you have max-version="17" it will work with all 17 versions.

Copy link
Member

@skjnldsv skjnldsv Aug 22, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because I want to be able to work with it in 18?
As soon as we branch off on server, this will be compatible with 17 and 18.
This pr will not be merged until 17 is released and branched off :)

Copy link
Member Author

@nickvergessen nickvergessen Aug 22, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well but it defeats totally the porpuse of the field if you put it in the app store like this.
Same as before. the old version in the app store says it's compatible with 17, but it isnt 🤷

Copy link
Member

@skjnldsv skjnldsv Aug 23, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, this release is a mistake :)
So I should just do min 17 max 17, right?

Copy link
Member Author

@nickvergessen nickvergessen Aug 23, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, and after stable17 is branched of you increase it in master

Copy link
Member

@skjnldsv skjnldsv Aug 23, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @nickvergessen :)

</dependencies>
<settings>
<admin>OCA\Preferred_Providers\Settings\Admin</admin>
<admin-section>OCA\Preferred_Providers\Settings\Section</admin-section>
<admin-section>OCA\Preferred_Providers\Settings\Section</admin-section>
</settings>
<background-jobs>
<job>OCA\Preferred_Providers\BackgroundJob\NotifyUnsetPassword</job>
<job>OCA\Preferred_Providers\BackgroundJob\ExpireUnverifiedAccounts</job>
<job>OCA\Preferred_Providers\BackgroundJob\NotifyUnsetPassword</job>
<job>OCA\Preferred_Providers\BackgroundJob\ExpireUnverifiedAccounts</job>
</background-jobs>
</info>