[WIP] SDK node rename to Framework#3461
Conversation
Pilchie
left a comment
There was a problem hiding this comment.
Looks okay, as long as we're all happy with making this change. Let's discuss a bit more in email to make sure everyone is happy with the change.
There was a problem hiding this comment.
Should probably rename this as well.
|
Why rename the Sdk node, the previous issue comments show that we need both SDK node and the Framework Node, so Why not keep the SDK node and duplicate the SDK node into Framework node and put the SDK node under a feature flag or something so that we can enable them when the SDK resolvers implement them?! It's just a waste to throw all of the work away! |
|
@Nirmal4G this is a point-in-time thing. We have no intention of releasing |
Codecov Report
@@ Coverage Diff @@
## master #3461 +/- ##
==========================================
+ Coverage 68.04% 68.05% +<.01%
==========================================
Files 726 727 +1
Lines 35805 35810 +5
Branches 2095 2095
==========================================
+ Hits 24364 24369 +5
Misses 11033 11033
Partials 408 408
Continue to review full report at Codecov.
|
|
We're going to approach this a different way; we are adding a framework node. |
Customer scenario
N/A
Bugs this fixes:
Part of #2248
Workarounds, if any
N/A
Risk
Low, just renaming of files and the SDK node
Performance impact
None, just renaming
Is this a regression from a previous update?
No
Root cause analysis:
N/A
How was the bug found?
Requests from team members