2019-06-16 18:39:31.709 WARN 41972 --- [ restartedMain] t.m.s.mapper.ClassPathMapperScanner : Skipping MapperFactoryBean with name '' and '....***' mapperInterface. Bean already defined with the same name!
I ran Jazzy locally on Serpent, and it looks like the documentation percentage is not very high. This is about documentation for functions that the users don't actually access, but still, for completeness and quality, we should document those too.
A zero-configuration, highly-configurable object-object mapper with viewable execution plans. Projects queries, transforms, deep clones, updates and merges via extension methods, or a static or instance API. Targets .NET Standard 1.0+ and .NET 3.5+
As the title says, it would be ideal if the route finder avoided critical/EOL wormholes. Perhaps this could be a setting, although I feel it should be the default setting if it is. Sometimes you find a route in one static, and the route finder will keep giving you that one because it's shorter, even though one of the holes may now be EOL or critical. When there might be another route that's longer
Is there a better and efficient way to perform the same operations the application does? Can the algorithms be improved to reduce resource usage and increase the performances?
Well, this is your occasion to start (or continue) your collaboration on the project adding your added value!
BULL wants you!