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

Make use_latent in duckling plugin configurable from project configs #202

Open
raina-rudra opened this issue Jul 6, 2023 · 0 comments
Open
Labels

Comments

@raina-rudra
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
In old architecture, we could pass latent_entities = true/false for each SLU independently, when creating the Input object. But with core slu service, this is not possible anymore.
Duckling picks this attribute of Input object to decide if we want to look for latent_entities or not, hence we need secondary way to pass this attribute.

Describe the solution you'd like
If we can make it so, that when declaring duckling_plugin in project_config repo of said SLU, we can pass activate_latent_entities as true/false, this problem can be fixed.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

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

No branches or pull requests

1 participant