-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EiffelTestExecutionRecipeCreatedEvent #41
Comments
As per eiffel-community#41. Note that there is a certain degree of inconsistency in the naming of this event in issues and documentation, respectively. The correct name is EiffelTestExecutionRecipeCollectionCreatedEvent.
As per eiffel-community#41. Note that there is a certain degree of inconsistency in the naming of this event in issues and documentation, respectively. The correct name is EiffelTestExecutionRecipeCollectionCreatedEvent.
As per eiffel-community#41. Note that there is a certain degree of inconsistency in the naming of this event in issues and documentation, respectively. The correct name is EiffelTestExecutionRecipeCollectionCreatedEvent.
Internal workshop review input: Given the current structure, assuming 10k recipes the event will end up on the order of 5MB, which is bad. It should be a protocol design principle that events should not contain properties of highly variable size which is likely to cause very large event sizes. For this particular event, the conclusion is that the TERC needs to be externally stored and linked via uri. However, a recommended format shall be provided (similar to what is currently proposed in the event). |
👍 |
As per eiffel-community#41. Note that there is a certain degree of inconsistency in the naming of this event in issues and documentation, respectively. The correct name is EiffelTestExecutionRecipeCollectionCreatedEvent.
Added EiffelTestExecutionRecipeCollectionCreatedEvent as per #41.
Added EiffelTestExecutionRecipeCollectionCreatedEvent as per #41.
Documentation and example required.
The text was updated successfully, but these errors were encountered: