Use fetch /me/calendarView for exact calendar reads in daily-outlook-triage#161
Open
solvaholic wants to merge 1 commit into
Open
Use fetch /me/calendarView for exact calendar reads in daily-outlook-triage#161solvaholic wants to merge 1 commit into
solvaholic wants to merge 1 commit into
Conversation
…triage
Reading meeting times through `ask` returns a bare, unlabeled, human-formatted
string that applies the zone's standard UTC offset rather than the current
daylight offset, so during DST months times can render an hour early with no way
for the caller to detect or correct it. Switch Step 3 to a structured
`fetch /me/calendarView` read, which returns each event as an unambiguous UTC
instant ({ dateTime, timeZone: "UTC" }) that converts DST-correctly, and add
guidance to convert the instant client-side, map Windows zone IDs to IANA, use
calendarView (not /me/events) for a date window, and read onlineMeeting.joinUrl
and responseStatus.response. Update the tools table and error-handling entries
to match.
Fixes microsoft#160
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Author
|
@microsoft-github-policy-service agree company="Microsoft" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #160
What
Switch Step 3 of the
daily-outlook-triageskill fromworkiq-askto a structuredworkiq-fetchon/me/calendarView, and add guidance to convert the returned UTC instant to the user's time zone client-side.Why
Per #160, reading meeting times through
askreturns a bare, unlabeled, human-formatted string ("12 PM to 1 PM") that appears to apply the zone's standard UTC offset rather than the current daylight offset - so during DST it can render an hour early, and the caller can't detect or correct it because the underlyingstart.dateTime/timeZoneisn't exposed.fetchon/me/calendarViewreturns each event as{ dateTime, timeZone: "UTC" }, an unambiguous instant that converts DST-correctly.Changes (docs-only, single skill file)
fetch /me/calendarViewwith$select/$orderby, and adds notes to:calendarViewnot/me/eventsfor a date window, so recurring occurrences expand;Eastern Standard TimefrommailboxSettings.timeZone) to IANA before converting - never format times viaask;onlineMeeting.joinUrland the response fromresponseStatus.response;$skip; follow@odata.nextLinkas a server-relative path.fetchalongsideask.Notes
ask- Documentfetch/calendarViewfor exact calendar reads —askreturns unlabeled, DST-prone meeting times #160 is specifically about the calendar time-read path.workiqskill ("Listing meetings on a known date/range ->fetch(/me/calendarView)").main; deliberately independent of the stalled Adding additional WorkIQ productivity skills #81.Verification
Docs-only change to a skill's guidance; no code or tests. Tool names,
entityUrlsshape, and/me/calendarViewusage cross-checked against theworkiqplugin'sfetch-work-iq.mdreference andSKILL.md.