You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Find a way to test the sqlite.go file without reimplementing 90% of the importer package (the importer is not sqlite specific). The problem here: the sqlite implementation reads from channels, which must be opened, closed and run concurrently
The text was updated successfully, but these errors were encountered:
The current implementation of the writer is not really good. It's not even possible to get an entity that produces the error. Maybe it's not too late yet to reimplement writers.
I'm ready to refactor code if you agree with me. I think writer method would receive only one entity and return an error, but it must be thread-safe. That approach would be easier to use and test.
Find a way to test the sqlite.go file without reimplementing 90% of the importer package (the importer is not sqlite specific). The problem here: the sqlite implementation reads from channels, which must be opened, closed and run concurrently
The text was updated successfully, but these errors were encountered: