Should unbloatable statements be considered formal requires for the output
opened this issue · comments
Deleted user commented
An unbloatable indicates an optional dependency between two INV.
Whether an unbloatable statement matched successfully or not, I don't think the log output should display a formal require text between the two INV.
Proposal for a new display:
formal: [INV] [my-owner] => [REQUIRE] [Something] formal
unbloatable: [INV] [UNBLOATABLE] [my-owner] => [REQUIRE] [Something] unbloatable
Also, it seems when's event could follow the same format, per example:
[INV] [WHEN] [my-owner] => [other-owner] name|tag
Deleted user commented
Unbloatables are not considered formal require statement anymore.
The implemented output:
[INV] [my-app] => [UNBLOATABLE] [Endpoint] my-unbloatable-ws-id
("UNBLOATABLE" is used instead of "REQUIRE")