I added a situation in which users might face both warnings and messages in the same analysis. This way, the users have some sort of context as opposed to the naked functions that produce the output, which they will almost never encounter unless they write production code.
I added a situation in which users might face both warnings and messages in the same analysis. This way, the users have some sort of context as opposed to the naked functions that produce the output, which they will almost never encounter unless they write production code.
Is this okay with you, @zachary-foster?