Skip to content
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.

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

Only accept folder setup page if overrideLocalDir is set #5385

Merged
merged 4 commits into from
Feb 2, 2023

Conversation

camilasan
Copy link
Member

Should fix #5383.

For reference please check #5329

@camilasan camilasan requested a review from mgallien February 1, 2023 20:47
@codecov
Copy link

codecov bot commented Feb 1, 2023

Codecov Report

Merging #5385 (c758cf8) into master (efa266f) will increase coverage by 0.02%.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #5385      +/-   ##
==========================================
+ Coverage   57.98%   58.01%   +0.02%     
==========================================
  Files         141      141              
  Lines       18113    18113              
==========================================
+ Hits        10503    10508       +5     
+ Misses       7610     7605       -5     
Impacted Files Coverage Δ
src/libsync/vfs/cfapi/cfapiwrapper.cpp 73.18% <0.00%> (+0.22%) ⬆️
src/libsync/discovery.cpp 86.21% <0.00%> (+0.28%) ⬆️
src/libsync/propagateremotemkdir.h 50.00% <0.00%> (+50.00%) ⬆️

Copy link
Collaborator

@claucambra claucambra left a comment

Choose a reason for hiding this comment

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

Just a nitpick

Comment on lines +343 to +352
{
// these config values will always be empty after the first client run
if (!_overrideServerUrl.isEmpty()) {
cfg.setOverrideServerUrl(_overrideServerUrl);
}

if (!_overrideLocalDir.isEmpty()) {
cfg.setOverrideLocalDir(_overrideLocalDir);
}
}
Copy link
Collaborator

@claucambra claucambra Feb 2, 2023

Choose a reason for hiding this comment

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

No variable declarations here, so I would say it makes sense to remove the block and make it inline with the rest of the method

If the intention here is to make it clear this is a specific procedure relating to override values, I would instead move it into a separate private static method which would make this even more readable

Camila added 4 commits February 2, 2023 08:43
Fix for #5383.

Signed-off-by: Camila <hello@camila.codes>
When the client runs for the first time, setting the value was done before
the config file was created. It had no effect.

Signed-off-by: Camila <hello@camila.codes>
Signed-off-by: Camila <hello@camila.codes>
@mgallien mgallien merged commit 69275bb into master Feb 2, 2023
@mgallien mgallien deleted the bugfix/issue-5383 branch February 2, 2023 07:44
@mgallien
Copy link
Collaborator

mgallien commented Feb 2, 2023

/backport to stable-3.6

@mgallien
Copy link
Collaborator

mgallien commented Feb 2, 2023

/backport to stable-3.7

@backportbot-nextcloud
Copy link

The backport to stable-3.6 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable-3.6
git pull origin/stable-3.6

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

# 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-stable-3.6

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

@backportbot-nextcloud
Copy link

The backport to stable-3.7 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable-3.7
git pull origin/stable-3.7

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

# 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-stable-3.7

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

@mgallien
Copy link
Collaborator

mgallien commented Feb 2, 2023

/backport to stable-3.7

@nextcloud-desktop-bot
Copy link

AppImage file: nextcloud-PR-5385-e533c6047c02cc717e77f1dd2af26217313ac459-x86_64.AppImage

To test this change/fix you can simply download above AppImage file and test it.

Please make sure to quit your existing Nextcloud app and backup your data.

@backportbot-nextcloud
Copy link

The backport to stable-3.7 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable-3.7
git pull origin/stable-3.7

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

# 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-stable-3.7

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

@sonarcloud
Copy link

sonarcloud bot commented Feb 2, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@szaimen
Copy link
Contributor

szaimen commented Feb 2, 2023

Looks like backports need ro be done manually today...

@mgallien mgallien added this to the 3.8.0 milestone Mar 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: nextcloud 3.6.6 or 3.7.0 rc1 does not allow to choose destination folder
5 participants