Skip to content

Conversation

staabm
Copy link
Contributor

@staabm staabm commented Oct 31, 2024

@staabm staabm force-pushed the invalid-string-offsets branch 2 times, most recently from 4da3b92 to 0d2e494 Compare October 31, 2024 09:09
@staabm staabm marked this pull request as ready for review October 31, 2024 09:16
@phpstan-bot
Copy link
Collaborator

This pull request has been marked as ready for review.

@staabm staabm force-pushed the invalid-string-offsets branch 2 times, most recently from ad6d064 to cde20cd Compare November 5, 2024 21:03
bleedingEdge: true
skipCheckGenericClasses!: []
stricterFunctionMap: true
reportPossiblyNonexistentStringOffset: true
Copy link
Contributor Author

@staabm staabm Nov 6, 2024

Choose a reason for hiding this comment

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

this might be enabled by default instead of using bleeding edge on 2.x, depending on how we decide here:
#3584 (comment)

@staabm staabm force-pushed the invalid-string-offsets branch from cde20cd to a3b8bdf Compare November 17, 2024 17:40
@clxmstaab clxmstaab force-pushed the invalid-string-offsets branch from a3b8bdf to c886a22 Compare December 20, 2024 09:15
@clxmstaab clxmstaab force-pushed the invalid-string-offsets branch from c886a22 to 08359ca Compare December 20, 2024 15:47
@staabm
Copy link
Contributor Author

staabm commented Jan 15, 2025

leaving a note for myself: double check how this PR and phpstan/phpstan#12122 make sense in combination

@staabm staabm closed this Jan 15, 2025
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.

Report invalid string offsets

3 participants