-
Notifications
You must be signed in to change notification settings - Fork 4
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
Compliance Update and Enable Update Panels #310
Compliance Update and Enable Update Panels #310
Conversation
@IsakNaslundBh , @kThorsager , @alelom this is now getting there. I've fixed a few things related to panel update, specifically the support/releases for the edges, which were not properly implemented before. One thing to check before fully test/merge:
More questions than answers :) I'm off tomorrow, so catch up Thursday/later this week. Either way not one to rush through given extent of change necessary. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really nice to get this in!
Some comments on some things that will need updating. Have just read the code, no tests yet.
Robot_Adapter/CRUD/Update/Panels.cs
Outdated
/**** Protected Methods ****/ | ||
/***************************************************/ | ||
|
||
protected override bool UpdateOnly<T>(IEnumerable<T> panels, string tag = "", ActionConfig actionConfig = null) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would not override this method, but just change it do an Update method that then can be dynamically called by the IUpdate mehtod. (similar principle as what we do with the Create)
By overriding this method UpdateOnly will only work for panels, but no other objects.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry missed that one... was still getting to grips with new adapter. Updated now and reran just to check - all ok. Have you seen my comments in message above? Line 165 and 193 in this cs file are relevant. I'm not sure it's 'correct' to be calling update on properties of dependent objects, and if it is, I don't think this approach is sustainable (and will have a big performance hit as it scales).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Testing if rebase possible
1c2c44c
to
1b8a57c
Compare
@IsakNaslundBh , I've tidied up this PR and network graph and I think/hope is ready for testing. Maybe one for us to talk/work though? Essentially final change is removing the auto-generated new properties when a named property (support/release) already exists, but returning a warning if we modify the named property in the model. Eventually I'd like to return 'one' warning to 'check push report' down the line - once we've built out the push report (returned as part of the 'success'). |
/azp run Robot_Toolkit.CheckCompliance |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've had a look at the compliance report on this and am requesting changes because there are a few files which do not appear to conform to current guidelines. Please review the report on the details for more information or reach out if anything is unclear 😄
Also, this PR needs an appropriate label (bug, feature, compliance, etc.) in addition to the size for the change log please.
Thanks @FraserGreenroyd , we were going to hold off the compliance updates for this/do it gradually. I see the tests are failing because we done a first pass (move cs files). Will see if I can try and add compliance changes too. @IsakNaslundBh I've found another issue with the adapter update cycle, so have added do not merge label again... sorry. Hopefully will fix tomorrow. |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Robot_Toolkit.CheckCompliance |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Robot_Toolkit.CheckCompliance |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm happy with this from a compliance perspective, thanks @rwemay - will allow @IsakNaslundBh the final approval from a functionality perspective 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks a lot better and all test runs works as good or better than before.
Would say lets get this merged, and if any bugs pop up, lets solve them later (do not think there should be any major induced by this PR)
/azp run Robot_Toolkit.CheckCompliance |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Robot_Toolkit.CheckInstaller |
Azure Pipelines successfully started running 1 pipeline(s). |
NOTE: Depends on
Issues addressed by this PR
Closes #308
Closes #301
Closes #250
Closes #184
Closes #249
Closes #319
Closes #318
Closes #321
Closes #322
Test files
Test files and models
Changelog
Additional comments