Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Composer Configuration #3

Open
yochay opened this issue Feb 1, 2019 · 1 comment
Open

Composer Configuration #3

yochay opened this issue Feb 1, 2019 · 1 comment

Comments

@yochay
Copy link

yochay commented Feb 1, 2019

for the bot section, you can figure out the 'provider' from the path?

with that said, where do all the node types and editor got, will they placed in the same composer file?

@boydc2014
Copy link
Owner

boydc2014 commented Feb 1, 2019

Sure we can get from path, usually this provider is not needed, if it's just local path, or even smb share.

It's only needed when special provider (not have a straightforwad file interface), and special config is needed, like key, connection string, tableName, i feel like we should explicitly specify the provider in that case. Such as

{
  provider: {
      type: "AzureCosmosDBProvider",
      collection: "xxxx"
  }
}

or 
{
  provider: {
    type: "AzureSQLProvider"
    connectionString: ""
    table: ""
  }
}

put the provider out of path, saying explicitly it's a provider which provides a file-based interface (even those it's sql behind), implying that whatever provider you are using, it will enable you to visit a path, and then relative paths.

then we use this file-based provider interface, start from the .bot file (or other project file), can use the reference in there to find, locate all dialog files, then load it.

the editor will get the loaded data from shell, the editor will not touch the files directly.

@yochay is that solve your question

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants