-
Notifications
You must be signed in to change notification settings - Fork 6
Offer #1013 remove force from nlu #4
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
base: pre-release
Are you sure you want to change the base?
Offer #1013 remove force from nlu #4
Conversation
erezbi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is 'Init' that you added? How did it work before you exposed it?
Also, what testing did you do on this?
|
@erezbi I just tried to run it a few times - We can run more tests if we want. |
|
does this need a change in the boilerplate then, to accompany it? |
|
yes, I need to update the example nlu engine as well |
|
So this will be a breaking change for all skills? they'll need to change something in the skills because of this change? |
|
no, this parameter isn't used. |
|
I was not referring to the 'force' parameter; i was referring to the fact that 'factory' was exposed, and some code depended on this. now it won't be exposed, so some code will need to change to use 'init' instead of 'factory'. is the code that needs to change in the skill BP? I am guessing it is because I didn't see it being changed in this commit. or, did you forget to change some other line - that used factory instead of 'init'? what am I missing here? |
|
Yes, you are correct.. |
|
is this breaking change needed? should we wait with this till we have a better reason for a breaking change? mind you, it would be even worse to break things after GA. |
|
Also, the 'force' isn't a breaking change. |
removed all the force parameters from the nlu objects
also unexposed factory