Cleanup usage of friendly_name in the code case to avoid future usage - #7272
Open
TimoPtr wants to merge 2 commits into
Open
Cleanup usage of friendly_name in the code case to avoid future usage#7272TimoPtr wants to merge 2 commits into
TimoPtr wants to merge 2 commits into
Conversation
Contributor
Test Results 338 files 370 suites 14m 24s ⏱️ Results for commit 2d9730a. ♻️ This comment has been updated with latest results. |
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.
Summary
This PR removes usage of the
friendly_nameattributes in the codebase mostly in tests so we don't rely on this anymore and new development too.Checklist
Select exactly one option that describes AI usage in this contribution: