Skip to content
This repository has been archived by the owner on Jun 28, 2023. It is now read-only.

LUIS CLI tool is unintuitive to use with model generators (like ludown) #927

Open
dkisselev opened this issue Jan 30, 2019 · 1 comment
Open
Assignees
Labels
approved Approved by the Triage Team enhancement New feature or request to evolve an existing feature luis-cli luis-cli issue P2

Comments

@dkisselev
Copy link

dkisselev commented Jan 30, 2019

Tool

Name: LUIS|ludown

Describe the problem

As a new LUIS/ludown user, I expect to be able to perform a flow such as ludown parse toluis... && luis update application --in... to quickly compile my ludown file and refresh the model I have defined in luis.

In practice, trying to accomplish this hit a number of roadblocks:

  • ludown docs never explicitly state what its json files represent. As a new user, I was first trying to perform luis update application before discovering that ludown files are best pushed at the version level.
    • In the portal ui, I opened my "Application" and started making changes (since the latest version is automatically selected), so I expected to simialrly be bale to push "application" changes in the CLI.
    • My generated json file and .luisrc also have an explicit version defined so luis update application should still work (and automatically traverse into the specified version).
  • luis update application and luis update version ONLY update the name and description, which is documented in the readme but very unintuitive (luis update version|application silently ignores model changes other than rename #926). The tool also returns "Success", but users see no changes in the UI.
  • There is no in-place update API for a luis application. Someone quickly iterating with ludown must follow the import-rename-delete flow as suggested in Luis replace version support  #633 (but must first discover that that's the only option).

Describe the solution you'd like

The linked issues in the LUIS CLI should be addressed (#633, #926) to significantly improve the usability of the luis tool together with ludown and other generators.

Users should be provided with additional quickstart documentation and pointers on how to go from a ludown-generated json file into an online LUIS model that they can easily continue updating.

Both tools are individually very well (and verbosely) documented, but there's a documentation gap when a user tries to turn their json file into a live model and continue iterating on it.

[enhancement]

@sgellock sgellock added 4.3 February 14, 2019 approved Approved by the Triage Team P2 labels Jan 30, 2019
@sgellock
Copy link
Member

@Kaiqb we'll want to make sure the 4.3 CLI changes coming address the documentation issues raised here

@Kaiqb Kaiqb assigned cahann and unassigned Kaiqb Feb 5, 2019
@cahann cahann removed the 4.3 February 14, 2019 label Feb 6, 2019
@vishwacsena vishwacsena added the ludown-cli ludown issue label Mar 5, 2019
@vishwacsena vishwacsena added luis-cli luis-cli issue and removed ludown-cli ludown issue labels Apr 2, 2019
@Kaiqb Kaiqb added customer-reported Required for internal Azure reporting. Do not delete. enhancement New feature or request to evolve an existing feature labels Jul 23, 2019
@sgellock sgellock removed the customer-reported Required for internal Azure reporting. Do not delete. label Aug 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Approved by the Triage Team enhancement New feature or request to evolve an existing feature luis-cli luis-cli issue P2
Projects
None yet
Development

No branches or pull requests

5 participants