Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Fix typo in ast.literal_eval usage#593

Open
SchnalzenbergerM wants to merge 1 commit into
microsoft:mainfrom
SchnalzenbergerM:patch-1
Open

Fix typo in ast.literal_eval usage#593
SchnalzenbergerM wants to merge 1 commit into
microsoft:mainfrom
SchnalzenbergerM:patch-1

Conversation

@SchnalzenbergerM

Copy link
Copy Markdown

there was a typo leading to not load the data

Pull Request

Pull Request (PR) description

Task list

  • The PR represents a single logical change. i.e. Cosmetic updates should go in different PRs.
  • Added an entry under the Unreleased section of in the CHANGELOG.md as per format.
  • Local clean build passes without issue or fail tests (build.ps1 -ResolveDependency -Tasks build, test).
  • Comment-based help added/updated.
  • Examples appropriately added/updated.
  • Unit tests added/updated..
  • Integration tests added/updated (where possible).
  • Documentation added/updated (where applicable).
  • Code follows the contribution guidelines.

there was a typo leading to not load the data
Copilot AI review requested due to automatic review settings June 29, 2026 08:59

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR fixes a typo in the notebook’s dataframe parsing logic so that stringified Python-literal lists in datasourceUsages are correctly converted into real Python lists using ast.literal_eval, aligning with how the notebook already performs the same conversion elsewhere.

Changes:

  • Replace incorrect astype.literal_eval call with ast.literal_eval when parsing df_dataflow_du['datasourceUsages'].
  • Ensure consistency with existing ast.literal_eval usage in the notebook (and import ast is already present).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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.

2 participants