Skip to content

v2.0 : Differiented between input and output strings on nullability rules in the format strategy configuraiton #154

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

Merged
merged 6 commits into from
May 27, 2024

Conversation

kevin-carroll
Copy link
Member

@kevin-carroll kevin-carroll commented Apr 29, 2024

  • Reworked the schema format strategy to be rules based and added many granular level rules to enforce common expectations via a builder pattern.
  • Removed .NET 7 support in anticipation of its deprecation

@kevin-carroll kevin-carroll added the v2.0 To be completed for the v2.0 release label Apr 29, 2024
@kevin-carroll kevin-carroll self-assigned this Apr 29, 2024
condensed name methods to 1 with an specifier parameter and extracted an interface for further customization
all type name formatting is done within the schema. no more magic strings.
@kevin-carroll kevin-carroll merged commit ae99fa2 into release/2.0 May 27, 2024
@kevin-carroll kevin-carroll deleted the feature-2/non-null-input-strings branch May 27, 2024 20:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v2.0 To be completed for the v2.0 release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants