Skip to content
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

adds readability / writability data for fields #169

Conversation

devmil
Copy link
Member

@devmil devmil commented Dec 27, 2023

Description

This PR adds readability and writability information to the model for fields and uses that information to extract more kinds of API changes.

Fixes #119

Type of Change

  • 🚀 New feature (non-breaking change)
  • 🛠️ Bug fix (non-breaking change)
  • ⚠️ Breaking change (feature or bug fix which breaks existing behaviors/APIs)
  • 🏗️ Code refactor
  • ⚙️ Build configuration change
  • 📝 Documentation
  • 🧹 Chore / Housekeeping

and uses that information in the comparison
…lity_and_writability_metadata_for_fields

# Conflicts:
#	CHANGELOG.md
#	test/package_api_storage_test.dart
- introduce full library name for return types
- adapt TypeIdentifier to consider dynamic for all utilities around nullable
- TypeHierarchy: rename "canBeAssigned" to "isCompatibleReplacement" which is a way better name for what we actually want to know + introduce "isTypePassedIn" and fix the functionality of this method
…data_for_fields

# Conflicts:
#	lib/src/model/executable_declaration.dart
#	lib/src/model/executable_declaration.freezed.dart
#	lib/src/model/field_declaration.freezed.dart
@devmil devmil merged commit 90bec51 into bmw-tech:main Feb 9, 2024
11 checks passed
@devmil devmil deleted the feature/add_readability_and_writability_metadata_for_fields branch February 9, 2024 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Removing a setter of a property is no breaking change
2 participants