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

HPCC-18222 DESDL refresh issue when overwriting #10555

Merged
merged 1 commit into from Oct 25, 2017

Conversation

miguelvazq
Copy link

@miguelvazq miguelvazq commented Oct 25, 2017

Whenever a navigates to a binding performs an action and then leaves and tries to perform another action the data from previous selection is still active.

Signed-off by: Miguel Vazquez miguel.vazquez@lexisnexis.com

Type of change:

  • This change is a bug fix (non-breaking change which fixes an issue).
  • This change is a new feature (non-breaking change which adds functionality).
  • This change improves the code (refactor or other change that does not change the functionality)
  • This change fixes warnings (the fix does not alter the functionality or the generated code)
  • This change is a breaking change (fix or feature that will cause existing behavior to change).
  • This change alters the query API (existing queries will have to be recompiled)

Checklist:

  • My code follows the code style of this project.
    • My code does not create any new warnings from compiler, build system, or lint.
  • The commit message is properly formatted and free of typos.
    • The commit message title makes sense in a changelog, by itself.
    • The commit is signed.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly, or...
    • I have created a JIRA ticket to update the documentation.
    • Any new interfaces or exported functions are appropriately commented.
  • I have read the CONTRIBUTORS document.
  • The change has been fully tested:
    • I have added tests to cover my changes.
    • All new and existing tests passed.
    • I have checked that this change does not introduce memory leaks.
    • I have used Valgrind or similar tools to check for potential issues.
  • I have given due consideration to all of the following potential concerns:
    • Scalability
    • Performance
    • Security
    • Thread-safety
    • Premature optimization
    • Existing deployed queries will not be broken
    • This change fixes the problem, not just the symptom
    • The target branch of this pull request is appropriate for such a change.
  • There are no similar instances of the same problem that should be addressed
    • I have addressed them here
    • I have raised JIRA issues to address them separately
  • This is a user interface / front-end modification
    • I have tested my changes in multiple modern browsers
    • The component(s) render as expected

Testing:

@hpcc-jirabot
Copy link

@@ -48,9 +48,7 @@ define([
idProperty: "__hpcc_id",

init: function (params) {
if (this.inherited(arguments))
return;

Copy link
Member

Choose a reason for hiding this comment

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

The Delay loader will spot and call "refresh" with the new params as needed, so do not remove the call to the base class, instead change:

         refresh: function () {
             this.refreshGrid();
         },

to:

         refresh: function (params) {
             this._params = params;
             this.refreshGrid();
         },

(You may need to also call the refreshState in there as well)

@miguelvazq
Copy link
Author

@GordonSmith Modified.

this._refreshActionState();
},

refresh: function () {
refresh: function (params) {
this._params = params;
this.refreshGrid();
Copy link
Member

Choose a reason for hiding this comment

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

@miguelvazq You may want to move the call to this._refreshActionState(); to inside the refresh function?

Copy link
Author

Choose a reason for hiding this comment

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

@GordonSmith Changed. Is this call required even if no event calls are being made on this particular grid? Tested and works as expected.

Whenever a navigates to a binding performs an action and then leaves and tries to perform another action the data from previous selection is still active.

Signed-off by: Miguel Vazquez <miguel.vazquez@lexisnexis.com>
@HPCCSmoketest
Copy link
Contributor

Automated Smoketest: ✅
Sha: 2547119
Build: success
Build: success
ECL Watch: Rebuilding Site

errors warnings build time
0 65 96.352 seconds

Install hpccsystems-platform-community_6.4.4-rc1.el7.x86_64.rpm
HPCC Start: OK

Unit tests result:

Test total passed failed errors timeout
unittest 96 96 0 0 0
wutoolTest(Dali) 19 19 0 0 0
wutoolTest(Cassandra) 19 19 0 0 0

Regression test result:

phase total pass fail
setup (hthor) 11 11 0
setup (thor) 11 11 0
setup (roxie) 11 11 0
test (hthor) 733 733 0
test (thor) 627 627 0
test (roxie) 760 760 0

HPCC Stop: OK
HPCC Uninstall: OK

@miguelvazq
Copy link
Author

@richardkchapman Tested and performing as expected. Had a minor question, OK to merge once approved.

Copy link
Member

@GordonSmith GordonSmith left a comment

Choose a reason for hiding this comment

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

Looks good.

@miguelvazq
Copy link
Author

@richardkchapman Ready to merge.

@richardkchapman richardkchapman merged commit 73be063 into hpcc-systems:candidate-6.4.4 Oct 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants