Original request was posted here.
We want the ensdb-sdk package to be useful for everyone building on ENSDb.
Therefore the ideas such as the following should be moved into ensdb-sdk:
DatabaseUrlSchemaEnsIndexerSchemaNameSchemaEnsDbConfigSchemaEnsDbConfig
Then, we could also move buildEnsDbConfigFromEnvironment to ensdb-sdk but the function signature would need to be better generalized so that it just took the database url and ensindexerschemaname as string params.
The call to buildEnsDbConfigFromEnvironment in apps/ensapi/src/config/ensdb-config.ts could then be easily updated to match the new signature.
Before addressing this issue, let's have the following issues resolved:
Original request was posted here.
We want the
ensdb-sdkpackage to be useful for everyone building on ENSDb.Therefore the ideas such as the following should be moved into
ensdb-sdk:DatabaseUrlSchemaEnsIndexerSchemaNameSchemaEnsDbConfigSchemaEnsDbConfigThen, we could also move
buildEnsDbConfigFromEnvironmenttoensdb-sdkbut the function signature would need to be better generalized so that it just took the database url and ensindexerschemaname as string params.The call to
buildEnsDbConfigFromEnvironmentinapps/ensapi/src/config/ensdb-config.tscould then be easily updated to match the new signature.Before addressing this issue, let's have the following issues resolved:
databaseSchematerm with a more precise one #1762databaseUrlwithensDbUrl#1763