Skip to content

Conversation

KobeW50
Copy link
Contributor

@KobeW50 KobeW50 commented Oct 3, 2025

No description provided.

@validcube validcube changed the title docs (Compose): Fix typos and settings order docs: Fix typos and settings order Oct 3, 2025
Copy link
Member

@validcube validcube left a comment

Choose a reason for hiding this comment

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

🥞📝 LGTM!

@KobeW50 KobeW50 marked this pull request as draft October 3, 2025 17:24
Enabling this will allow you to change the patch selection
> ⚠️ Warning
> Changing the selection may cause unexpected issues.
> Unless you know what you are doing, it is recommended to keep this disabled.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

In 1.26.0-dev.7, this option is enabled by default. Is that a bug, or does this warning need to be changed?

Copy link
Member

Choose a reason for hiding this comment

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

That is enabled by default yes, this is not "expected", I already notified the team in discord.

@KobeW50 KobeW50 marked this pull request as ready for review October 3, 2025 17:33
@ILoveOpenSourceApplications

Please look into #2780 (comment) as well.

@Ushie
Copy link
Member

Ushie commented Oct 3, 2025

Settings aren't considered final, this PR should be postponed

@Ushie Ushie marked this pull request as draft October 3, 2025 18:12
<string name="auto_update_description">Automatically update when a new version is available</string>
<string name="patches_prereleases">Use pre-releases</string>
<string name="patches_prereleases_description">Use pre-release version of %s</string>
<string name="patches_prereleases_description">Use pre-release versions of %s</string>

Choose a reason for hiding this comment

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

Suggested change
<string name="patches_prereleases_description">Use pre-release versions of %s</string>
<string name="patches_prereleases_description">Use pre-release version of %s</string>

Isn't it better to use version at both places?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

In that case the toggle titles will also need to be singular. Currently they are plural ("Use pre-releases")

Also, I think "versions" better reflects that the patches and Manager are constantly updated. There isn't a single pre-release version. Rather, it is constantly changing. Not sure if I'm explaining myself well. I understand your perspective too 😅

@KobeW50
Copy link
Contributor Author

KobeW50 commented Oct 3, 2025

Settings aren't considered final, this PR should be postponed

Isn't it best to have it reflect the current state of settings? If the settings are changed, a new PR can be opened in the future.

I wish not to have this PR hang open, because then I will be responsible to reflect all future changes and mistakes. I don't like putting workloads on myself, so I was hoping this would quickly be merged or closed.

Same for my other PR: #2791

@validcube
Copy link
Member

Settings aren't considered final, this PR should be postponed

I don't think this PR should be postponed, this PR is relating to the current branch dev not the settings V2 refactor branch, the owner of the refactor branch should be the one updating the documentation instead.

@Ushie Ushie marked this pull request as ready for review October 5, 2025 23:12
Copy link
Member

@validcube validcube left a comment

Choose a reason for hiding this comment

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

🥞 LGTM! (latest versions)

@validcube validcube merged commit d188d5a into ReVanced:dev Oct 17, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants