-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
enable conversation sessions by default #6934
Changes from 2 commits
967eefe
3ee3572
d3e0019
dd6cf18
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
[Conversation sessions](domain.mdx#session-configuration) are now enabled by default | ||
if your [Domain](domain.mdx) does not contain a session configuration. | ||
Previously a missing session configuration was treated as if conversation sessions | ||
were disabled. You can explicitly disable conversation sessions using the following | ||
snippet: | ||
|
||
```yaml-rasa title="domain.yml" | ||
session_config: | ||
# A session expiration time of `0` | ||
# disables conversation sessions | ||
session_expiration_time: 0 | ||
``` |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -86,7 +86,6 @@ class SessionConfig(NamedTuple): | |
|
||
@staticmethod | ||
def default() -> "SessionConfig": | ||
# TODO: 2.0, reconsider how to apply sessions to old projects | ||
return SessionConfig( | ||
rasa.shared.constants.DEFAULT_SESSION_EXPIRATION_TIME_IN_MINUTES, | ||
rasa.shared.constants.DEFAULT_CARRY_OVER_SLOTS_TO_NEW_SESSION, | ||
|
@@ -185,7 +184,6 @@ def from_dict(cls, data: Dict) -> "Domain": | |
def _get_session_config(session_config: Dict) -> SessionConfig: | ||
session_expiration_time_min = session_config.get(SESSION_EXPIRATION_TIME_KEY) | ||
|
||
# TODO: 2.0 reconsider how to apply sessions to old projects and legacy trackers | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I guess we've just decided to leave them as is? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No, I changed the default from There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. i guess i assumed that this note was about "should we read all of the conversations from 2018 as one conversation even if we introduce sessions now? with regards to applying them to legacy trackers There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah, okay. Yes, these will have sessions enabled, too, now |
||
if session_expiration_time_min is None: | ||
session_expiration_time_min = ( | ||
rasa.shared.constants.DEFAULT_SESSION_EXPIRATION_TIME_IN_MINUTES | ||
|
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.
The title of the targeted section is currently
Session Configuration
. I'd vote for renaming this toConversation Sessions
.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.
@erohmensing ?
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.
Mm, I think it makes the most sense to have the title of the section to reflect the high level keys in the domain
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.
Okay, then let's leave it as it is.