This repository was archived by the owner on Mar 6, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 324
fix: make AccessEntry equality consistent with from_api_repr #2218
Merged
Merged
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
969f09f
fix: make AccessEntry equality consistent for view entity type
drokeye 0dc6b35
fix: make AccessEntry equality consistent for view entity type
drokeye 7687693
fix: use json.dumps() for normalizaiton of entity_id
drokeye 6ab2c3c
remove trailing whitespace and add test assertions
drokeye 33c01b5
Merge branch 'main' into fix-accessentry-equality
Linchin 6baa50b
revert back to the original code
drokeye 949aa3c
Merge branch 'fix-accessentry-equality' of https://github.com/drokeye…
drokeye 266989a
Merge branch 'main' into fix-accessentry-equality
Linchin adffcf5
fix linting in `dataset.py`
drokeye 4230a9d
fix linting in `test_dataset.py`
drokeye 12fae55
Merge branch 'main' into fix-accessentry-equality
Linchin 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
remove trailing whitespace and add test assertions
- Loading branch information
commit 6ab2c3c79779ac9c55e82de01deecc8154030a6e
There are no files selected for viewing
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.
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.
Similar to https://github.com/googleapis/python-bigquery/pull/2218/files#r2162644585, could you explain why we need to manually copy the resource dict? It doesn't seem very future-proof if we add any new fields in the future. Also, we deliberately used
resource.copy()to make a shallow copy, mostly in order to reduce complexity and increase speed. Is deepcopy necessary here?Uh oh!
There was an error while loading. Please reload this page.
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.
I originally switched to a manual copy/deepcopy mainly to help isolate issues during tests, especially with view/routine equality, where we needed full round-trip consistency via
_properties. But I agree, it's my bad it's not ideal. Reverted this back to the original code.