Skip to content
This repository was archived by the owner on Jan 15, 2025. It is now read-only.
This repository was archived by the owner on Jan 15, 2025. It is now read-only.

Issues of build and cross-train cli #800

@feich-ms

Description

@feich-ms

Versions

What CLI version are you using.
What Nodejs version are you using
What command-line interpreters are you using
What OS are you using

Describe the bug

Luis:build

  1. Luis:build and qnamaker:build do not write .dialog if no –out is specified.
  2. –suffix when not specified resulted in LUIS app with (Undefined).
  3. Verify luis:build detects changes to references.
  4. Fix issue with config relative path. Relative path must always be relative to the CWD()5
  5. C:\users\temp> bf luis:build –in . –out generated –config ..\foo.config.json

Luis:cross-train

  1. -- config is relative to –in and not relative to the pwd()
  2. Cross-train config is file name case sensitive.
  3. Cross-train should only copy over files specified in the cross-train config to output but all references should be fully resolved before they are copied over.
  4. QnA meta-data property is not applied to references
  5. Apply cross-train for .lu and .qna documents after fully resolving imports.
  6. If multiple source .lu or .qna files are pulling in the same reference, the for QnA, meta-data pairs need to be added to the same QnA pair (e.g. root as well as dialog A pulling in some chitchat utterances)

Qnamaker:build

  1. There is no way to get endpoint key. We should print this on screen. Note the endpoint key is different from authoring key and I believe is per KB – need to verify and resolve.
  2. Fix issue with config relative path. Relative path must always be relative to the CWD()

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

Give a clear and concise description of what you expected to happen.

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

[bug]

Metadata

Metadata

Assignees

Labels

R10Release 10 - August 17th, 2020

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions