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

Add support for Fluent Assertions v8 #132

Merged
merged 2 commits into from
Jan 20, 2025

Conversation

adrianiftode
Copy link
Owner

@adrianiftode adrianiftode commented Jan 20, 2025

Add support for FluentAssertions v 8.0.0

Will maintain both Fluent Assertions v7 FOSS and Paid Fluent Assertions v8

  • code for v8 will always be in master-fluent-assertions-v8
  • new nuget packages: FluentAssertions.Web.v8 and FluentAssertions.Web.v8.Serializers.NewtonsoftJson
  • still thinking on the name (FluentAssertions.Web.xceed maybe?)
  • might not be able to use the nuget FluentAssertions prefix, to ask for permission, it that's even possible

Addressing #130 and fluentassertions/fluentassertions#2943

@adrianiftode adrianiftode changed the base branch from master to master-v8 January 20, 2025 14:17
@adrianiftode
Copy link
Owner Author

I'll probably change the approach to still use master, but add conditional preprocessor directives to handle v7 vs v8

@adrianiftode adrianiftode force-pushed the master-fluent-assertions-v8 branch 2 times, most recently from 2d2ebf0 to 0656949 Compare January 20, 2025 23:01
@adrianiftode adrianiftode changed the base branch from master-v8 to master January 20, 2025 23:01
@adrianiftode adrianiftode force-pushed the master-fluent-assertions-v8 branch from 0656949 to 70f9c2f Compare January 20, 2025 23:06
@adrianiftode adrianiftode force-pushed the master-fluent-assertions-v8 branch from 70f9c2f to d3a6e41 Compare January 20, 2025 23:10
@adrianiftode adrianiftode merged commit 59b23af into master Jan 20, 2025
1 check passed
@adrianiftode adrianiftode deleted the master-fluent-assertions-v8 branch January 20, 2025 23:21
@adrianiftode adrianiftode linked an issue Jan 20, 2025 that may be closed by this pull request
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.

Still compatible with FA v8?
1 participant