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

fix: Clear fetched field when link field is cleared #15343

Merged
merged 5 commits into from Dec 22, 2021

Conversation

sumaiya2908
Copy link
Contributor

@sumaiya2908 sumaiya2908 commented Dec 17, 2021

Issue
When the link field is cleared, the docfield which is fetched from the link field remains the same as the previous value and gets saved.

Before
the 'Name' field is read-only.

Screen.Recording.2021-12-17.at.9.17.18.AM.mov

After

Screen.Recording.2021-12-17.at.9.18.22.AM.mov

Steps to reproduce

  1. Create/go to any doctype with a link field and a field that is fetched from the link field.
  2. Select a value for the link field, you will see the value being fetched in the other field.
  3. Now clear the link field.
    a. Expected Result: the field which is being fetched, should be cleared.
    b. Actual Result: it remains the same as the previous value and gets saved.

@sumaiya2908 sumaiya2908 requested a review from a team as a code owner December 17, 2021 03:56
@sumaiya2908 sumaiya2908 requested review from surajshetty3416 and removed request for a team December 17, 2021 03:56
@surajshetty3416 surajshetty3416 changed the title fix: clear fetched field when link field is cleared fix: Clear fetched field when link field is cleared Dec 17, 2021
Copy link
Member

@surajshetty3416 surajshetty3416 left a comment

Choose a reason for hiding this comment

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

@sumaiya2908 the fix does not work with this change #15320

You might have to update the code

@surajshetty3416
Copy link
Member

@Mergifyio backport version-13-hotfix

@mergify
Copy link
Contributor

mergify bot commented Dec 22, 2021

backport version-13-hotfix

🟠 Waiting for conditions to match

  • merged [:pushpin: backport requirement]

@codecov
Copy link

codecov bot commented Dec 22, 2021

Codecov Report

Merging #15343 (f8cbe95) into develop (4f38b7d) will increase coverage by 1.01%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop   #15343      +/-   ##
===========================================
+ Coverage    49.78%   50.80%   +1.01%     
===========================================
  Files          745      742       -3     
  Lines        65234    65320      +86     
  Branches      5419     5432      +13     
===========================================
+ Hits         32479    33186     +707     
+ Misses       28825    28272     -553     
+ Partials      3930     3862      -68     
Flag Coverage Δ
ui-tests 38.16% <100.00%> (+2.98%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

@mergify mergify bot merged commit d1e229d into frappe:develop Dec 22, 2021
@mergify
Copy link
Contributor

mergify bot commented Dec 22, 2021

backport version-13-hotfix

❌ No backport have been created

  • Backport to branch version-13-hotfix failed
    Pull request with merge commit are not supported

@gavindsouza
Copy link
Collaborator

@sumaiya2908 A support ticket was raised for Frappe v14 (develop) even though we haven't started stable releases for it?

@sumaiya2908
Copy link
Contributor Author

@gavindsouza the issue was raised for v13. And when I checked, it existed in develop too. So I raised a PR for develop, and then backported it.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants