Conversation
@RazzM13 is this still WIP? |
Hi @martysweet, basically I already have the code for this now (needs a bit of cleaning up though) but I believe that some changes will be required to integrate with SAM that relate to work items 2 and 3 and therefore I was hoping to delay this until SAM support is in, in order to avoid some merge conflicts. How do you feel about it? |
I was actually wondering about that too, though I haven't really had a chance to look at the changes imposed by #156, perhaps @akdor1154 can shed some light upon the matter ... |
Hey @martysweet, now that SAM support is in |
68d2f05
to
7fdef30
Compare
…hat exhibits a dual role of notifying a user about the mocked values that are in play as well as keeping track of potential value conflicts for the same attribute that may arrise during runtime and, notifying if such a conflict occurs.
…tual resource attributes and parameters.
Hey @martysweet, just managed to implement the centralized mocking functions based on the attribute type as well as contextual resolution (place within intrinsic or within a given resource/property type). I believe that we've now fully covered the proposed enhancements of #160 therefore, please have a look over everything and let me know if something is missing, incorrect or otherwise. One thing that I feel I should mention is that we don't currently have support for mocking entire structures (i.e. resource / resource-property types), I believe that this shouldn't really be too difficult to add however, I'm not really sure of how much use this may be... PS: I've noticed that |
Hey @martysweet, apart from the merge conflict is there anything else that is blocking this? :) |
Fixes #160