skylight.sessions) as its context, with an adapter that sorts the sessions by their current state (placing those that have properties.state === 'inprogress' before those that have properties.state === 'complete'. While the name and state of the session are displayed, note that we cannot display information in the session data because that requires having the session set as the current session. Selecting this card brings up two actions:sessionView.properties.state value between the strings inprogress and complete.properties.state of the currently-set sessions.properties.state value between the strings inprogress and complete.session.data.countsession.data.otherCountsession.data.count and session.data.otherCountskylight.session.update can be used to update the session's properties object. However, other parts of the sessions (such as its name and description) can be modified as well. That said, participants are added and removed using the skylight.session.addParticipant and skylight.session.removeParticipant methods.skylight.session.saveData method rather than the skylight.session.update method, as seen in the count increment card scripts.skylight.session.update method overwrites the existing value for whatever session property is specified. This is particularly important to note when updating the session.properties property, as the entire object will be overwritten (unlike the way that skylight.session.saveData operates, which patches the object). The best practice is to retrieve the existing properties object, create a copy of it (as it is immutable), modify the copy, then call skylight.session.update with the modified copy of the session's properties.properties specified, it is recommended to assume that there may exist sessions where properties is undefined.