Skip to content

Conversation

@susnux
Copy link
Contributor

@susnux susnux commented Nov 25, 2025

  • update config
  • auto fix issues
  • base line legacy issues

Checklist

@susnux susnux requested a review from skjnldsv as a code owner November 25, 2025 13:14
@susnux susnux added the 3. to review Waiting for reviews label Nov 25, 2025
@susnux susnux requested review from a team as code owners November 25, 2025 13:14
@susnux susnux added dependencies ♻️ refactor Refactor code (not a bug fix, not a feature just refactoring) labels Nov 25, 2025
@susnux susnux requested review from leftybournes, nfebe, salmart-dev, szaimen and yemkareems and removed request for a team November 25, 2025 13:14
Copy link
Contributor

@szaimen szaimen left a comment

Choose a reason for hiding this comment

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

🐘

@susnux susnux added this to the Nextcloud 33 milestone Nov 25, 2025
Comment on lines +16 to 17
:model-value="value"
@input="onInput" />
Copy link
Contributor

Choose a reason for hiding this comment

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

We probably should also check the events in the plugin.

<template>
<fieldset class="permissions-select">
<NcCheckboxRadioSwitch :checked="canCreate" @update:checked="toggle(PERMISSION_CREATE)">
<NcCheckboxRadioSwitch :model-value="canCreate" @update:checked="toggle(PERMISSION_CREATE)">
Copy link
Contributor

Choose a reason for hiding this comment

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

Setting modelValue but handling update:checked feels incorrect even it works

Copy link
Contributor Author

Choose a reason for hiding this comment

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

BTW we still do not support @update:model-value this is never emitted. Only @update:modelValue is for Vue 2.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Setting modelValue but handling update:checked feels incorrect even it works

(Rebased and additionally) added a new commit manually adjusting those events.

Copy link
Contributor

Choose a reason for hiding this comment

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

BTW we still do not support @update:model-value this is never emitted. Only @update:modelValue is for Vue 2.

Are you sure?
The migration composable doe emit it. It is only skipped in components initially using update:modelValue

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was pretty sure that it did not work when I was testing it, but now I cannot reproduce 🤔

@susnux susnux force-pushed the chore/eslint-config branch from 19ac884 to 6bcc00d Compare November 25, 2025 14:27
@susnux
Copy link
Contributor Author

susnux commented Nov 25, 2025

/compile

@susnux susnux force-pushed the chore/eslint-config branch from 6bcc00d to f1d2833 Compare November 25, 2025 15:25
Signed-off-by: nextcloud-command <[email protected]>
@susnux susnux merged commit 8b293d1 into master Nov 25, 2025
155 of 159 checks passed
@susnux susnux deleted the chore/eslint-config branch November 25, 2025 18:40
@skjnldsv
Copy link
Member

skjnldsv commented Dec 10, 2025

Since this PR I get errors like those when opening the basic settings @susnux :

image

@susnux
Copy link
Contributor Author

susnux commented Dec 10, 2025

Since this PR I get errors like those when opening the basic settings

I cannot see any changed for value props but both messages look like they are always an error, because this PR did not touch any casting of values.

But where did you see this messages? I looked through all settings and could not find this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews dependencies ♻️ refactor Refactor code (not a bug fix, not a feature just refactoring)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants