-
Notifications
You must be signed in to change notification settings - Fork 0
fix(focalpoint): vendor observability macro crate #80
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
Closed
Closed
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
78dff7e
fix(focalpoint): vendor observability macro crate
KooshaPari 1698603
fix(focalpoint): repair all-features MCP build
KooshaPari c647dfb
test(focalpoint): use public MCP tools API
KooshaPari f543863
fix(focalpoint): clear Notion and RustSec CI blockers
KooshaPari 994943e
chore(focalpoint): relax cargo-deny wildcards
KooshaPari 522aeb4
fix(focalpoint): repair Readwise parser tests
KooshaPari c650bd7
fix(focalpoint): stabilize focus-cli JSON outputs
KooshaPari 2f92e99
test(focalpoint): mark unimplemented spec stubs as ignored
KooshaPari 7cd298b
Merge origin/main into PR #80 branch (focalpoint-observably-vendor)
KooshaPari File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
🧩 Analysis chain
🌐 Web query:
In the Notion API page properties schema, for a property of type "status", where is the status name stored (e.g.,status.namevsselect.name)?💡 Result:
In the Notion API, for a property of type "status," the status name is stored in
status.name[1][2]. When accessing a page property value, the object contains atypefield (set to "status") and a correspondingstatusobject [1]. Thestatusobject contains the specific data for that property, including thenamefield, which holds the string value of the status as it appears in Notion [1]. For example, when retrieving a page, the response structure for a status property appears as follows [2]: { "Status": { "id": "...", "type": "status", "status": { "id": "...", "name": "In progress", "color": "blue" } } } Similarly, when updating or creating a status property value, you use thestatusobject in your request body [1]: { "properties": { "Status": { "status": { "name": "Not started" } } } }Citations:
Fix Notion “status” completion parsing to read
status.status.namestatus_donecurrently traversesstatus -> select -> name, but Notion “status” property values store the label understatus -> status -> name(e.g.,{ "type": "status", "status": { "name": "In progress" } }), which can cause done tasks to be parsed as incomplete.Proposed fix
let status_done = properties .get("status") - .and_then(|s| s.get("select")) + .and_then(|s| s.get("status").or_else(|| s.get("select"))) .and_then(|s| s.get("name")) .map(|status| status.eq_ignore_ascii_case("done")) .unwrap_or(false);Add a regression test that uses a Notion-like
"status"property value payload.🤖 Prompt for AI Agents