Move deprecation warnings to debug

[szaimen]

Same as #37816 but for js

[ChristophWurst]

Debug logs and debug mode only

[szaimen]

@ChristophWurst addressed

[szaimen]

/compile /

[ShGKme]

In browsers debug log is hidden by default. If some app developers are using deprecated stuff, they will know about it only if they directly turn on the verbose log level. Is it intended?

And there will be no difference between important deprecation warning messages from the libs and verbose debug logs for app/lib in terms of log levels.

[szaimen]

And there will be no difference between important deprecation warning messages from the libs and verbose debug logs for app/lib in terms of log levels.

that is what I was wondering about as well. So my suggestion would be to show these as warnings if debug mode is enabled. WDYT?

[ShGKme]

that is what I was wondering about as well. So my suggestion would be to show these as warnings if debug mode is enabled. WDYT?

I'd either keep console.warn for deprecation warnings or make something more high-level.

[szaimen]

I'd either keep console.warn for deprecation warnings or make something more high-level.

please check out 6dd433a

[skjnldsv]

/compile amend /

[szaimen]

/backport to stable27

[backportbot-nextcloud]

The backport to stable27 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable27
git pull origin stable27

# Create the new backport branch
git checkout -b fix/foo-stable27

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable27

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

[szaimen]

/backport to stable27

[backportbot-nextcloud]

The backport to stable27 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable27
git pull origin stable27

# Create the new backport branch
git checkout -b fix/foo-stable27

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable27

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

[szaimen]

#38980