Official web-based GUI client for evitaDB e-commerce database. It is built to help developers who use evitaDB with exploring and debugging their domain structure and data. Besides standard query executing, it also supports multiple no-code tools to quickly navigate through domain structure, docs and data without needing to write any queries.
In #94, the evitaDB driver concept were introduced to support different versions of evitaDB server versions within single evitaLab version. For this, an internal model representing evitaDB's model were introduced with Value class representing a evitaDB model value that may not be supported by chosen driver version (server version). Its primary purpose is to disable parts of the UI for which the used evitaDB server version has no data. The UI must have some way to tell the user that certain part is not supported by the chosen driver.
Currently, the unsupported values are handled as if they were empty but supported, which is temporary simple solution but not desired. This issue will change that.
In #94, the evitaDB driver concept were introduced to support different versions of evitaDB server versions within single evitaLab version. For this, an internal model representing evitaDB's model were introduced with
Valueclass representing a evitaDB model value that may not be supported by chosen driver version (server version). Its primary purpose is to disable parts of the UI for which the used evitaDB server version has no data. The UI must have some way to tell the user that certain part is not supported by the chosen driver.Currently, the unsupported values are handled as if they were empty but supported, which is temporary simple solution but not desired. This issue will change that.