Skip to content
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

Allow the user to provide "describers" on a per-handler basis. #202

Open
jmalloc opened this issue Nov 26, 2020 · 2 comments
Open

Allow the user to provide "describers" on a per-handler basis. #202

jmalloc opened this issue Nov 26, 2020 · 2 comments

Comments

@jmalloc
Copy link
Member

jmalloc commented Nov 26, 2020

It might be useful if the user could provide a function that can describe the current state of a projection (or perhaps any other handler) so that it can be observed when a test fails and/or between each engine dispatch/tick.

I am not sure how much merit this idea has; specifically, I wouldn't want devs to spend forever writing and updating code that exports SQL database state in a human readable format. For SQL projectionkit could help with that, but obviously projections are not limited to any particular storage technology.

This is also potentially a LOT of data, possibly too much to include in an expectation report, but I suppose it could be written to disk and the expectation report could print the file location. Another option would be to reimplement some kind of verbose option.

@jmalloc jmalloc changed the title Allow the user to provide "state describers" on a per-handler basis. Allow the user to provide "describers" on a per-handler basis. Nov 26, 2020
@jmalloc
Copy link
Member Author

jmalloc commented Nov 26, 2020

We might need to look at #5 for this feature to be very useful.

@jmalloc
Copy link
Member Author

jmalloc commented Nov 26, 2020

This could be done in a VERY generic way by simply having a function that returns some content that is diffed each time a fact occurs. It wouldn't even need to be aware of handlers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant