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
Finish implementing scenarios defined in vuu.util.schema.SchemaMapperFunctionalTest for in memory table. May want to use the result pattern for reporting helpful error message
Test around defining ignite CacheConfiguration Query Entity column order vs ScheamMapper external entity column order -> what happens if they are different? The list of value returned from ignite query return in order of the configuration? Is that order respected when creating ExternalEntitySchema in the Field Index?
See vuu.feature.igniteSchemaMapperFunctionalTest for the virtual table - need to finish writing this test and it need to include other features that uses the schema mapper such as the filtering & type ahead. Also need to write more edge case tests for virtual table usages
Others outstanding tasks
SchemaMapperJavaFunctionalTest should use FakeDataSource that is in Java rather than Scala to be more accurate reflection of Java VUU usecase
ColumnValueProvider need to convert the typeahead values to column type before sending results to ui if different from entity field type
Review ScalaCollectionConverter.java usage see if best to provide this util as java or scala given its purely used by java clients of VUU
Review usages if SchemaMapper.toInternalRowMap(externalDto: Product): Map[String, Any] function which takes in the entity object and remove if no longer needed. if we get back list of values from the data source(ignite), we can map that straight to a map using toInternalRowMap(externalValues: List[_]): Map[String, Any] without converting to an entity first.
To write vuu.feature.igniteSchemaMapperFunctionalTest need to add vitualized-table-plugin module as dependency to ignite-plugin as currently don't have any non-example/demo code that reference both. We need to be able to test them together - as intended to be used as part of the core library to prevent any regression & help with testing. Need to decide how to structure these and how best to test. These are related to ongoing discussion issue 989 and spike of pluggable project structure pull request 1018
The text was updated successfully, but these errors were encountered:
Finish writing tests for different usecases
vuu.util.schema.SchemaMapperFunctionalTest
for in memory table. May want to use the result pattern for reporting helpful error messagevuu.feature.igniteSchemaMapperFunctionalTest
for the virtual table - need to finish writing this test and it need to include other features that uses the schema mapper such as the filtering & type ahead. Also need to write more edge case tests for virtual table usagesOthers outstanding tasks
SchemaMapperJavaFunctionalTest
should useFakeDataSource
that is in Java rather than Scala to be more accurate reflection of Java VUU usecaseColumnValueProvider
need to convert the typeahead values to column type before sending results to ui if different from entity field typeScalaCollectionConverter.java
usage see if best to provide this util as java or scala given its purely used by java clients of VUUSchemaMapper.toInternalRowMap(externalDto: Product): Map[String, Any]
function which takes in the entity object and remove if no longer needed. if we get back list of values from the data source(ignite), we can map that straight to a map usingtoInternalRowMap(externalValues: List[_]): Map[String, Any]
without converting to an entity first.vuu.feature.igniteSchemaMapperFunctionalTest
need to add vitualized-table-plugin module as dependency to ignite-plugin as currently don't have any non-example/demo code that reference both. We need to be able to test them together - as intended to be used as part of the core library to prevent any regression & help with testing. Need to decide how to structure these and how best to test. These are related to ongoing discussion issue 989 and spike of pluggable project structure pull request 1018The text was updated successfully, but these errors were encountered: