feat: add notices to contract publishing response, with intent to rem… #430
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm replacing the "logs" in the contract publishing response with "notices", so as to be consistent with the notices in the "pacts for verification" endpoint, and so that there can be a better representation of intent behind the messages. The log messages with a level of
warn
,info
,debug
will be replaced with notices withtype
ofsuccess
,info
,warning
,error
anddebug
(in the style of bootstrap alerts).I'm mapping
success
to green,warning
to yellow,error
to red.info
anddebug
are uncoloured. Not 100% sure about the need for debug, but wondering if things get too noisy, that might be able to be turned off. I'm currently usingwarning
for the "you should do this next" kind of notices, but I'm going to think of a better name for that soon, which I'm thinking might map to blue.Haven't removed the logs yet, so as to keep the pacts green, but will once this is out in prod.