Skip to content

Bam masterdata runtime selection - #97

Open
JosePizarro3 wants to merge 7 commits into
developfrom
bam-masterdata-runtime-selection
Open

Bam masterdata runtime selection#97
JosePizarro3 wants to merge 7 commits into
developfrom
bam-masterdata-runtime-selection

Conversation

@JosePizarro3

Copy link
Copy Markdown
Collaborator

(rebasing of #81)

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7bd5eb6020

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 517 to 519
if allow_cross_module:
return True
# same module only if cross-mod disabled
return module.startswith(base_namespace)
return module.startswith(base_namespace)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Re-enable cross-module traversal when enabled

The allow_cross_module switch is effectively ignored because both branches now require module.startswith(base_namespace). With allow_cross_module=true, graph expansion should include related classes outside the base namespace (e.g., inherited or subsection targets), but this change silently filters them out and breaks the UI’s cross-module mode. This is a functional regression in graph completeness.

Useful? React with 👍 / 👎.

Comment thread api/light_mode/app.py
async def schema_update():
async def schema_update(profile: str | None = Query(None)):
ws = _workspace()
selected = schema_profile_for_key(profile) if profile else _profile_for_workspace(ws)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Handle unknown schema profile as a client error

schema_profile_for_key(profile) can raise SchemaUnavailable for invalid profile keys, but it is called outside the try block, so /schema/update?profile=<invalid> surfaces as an unhandled 500 instead of a controlled API error. A stale or mistyped profile from clients will therefore fail with an internal error and no actionable response code.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant