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 a new configuration option for required field generation #381

Merged

Commits on Mar 18, 2024

  1. Add a new `Required configuration option

    Signed-off-by: Sergen Yalçın <yalcinsergen97@gmail.com>
    sergenyalcin committed Mar 18, 2024
    Configuration menu
    Copy the full SHA
    bdfbe67 View commit details
    Browse the repository at this point in the history

Commits on Mar 19, 2024

  1. - Move the config.ExternalName.RequiredFields to config.Resource.requ…

    …iredFields
    
    - Deprecate config.MarkAsRequired in favor of a new configuration function on *config.Resource that still accepts a slice to mark multiple fields as required without doing and invervention in native field schema.
    
    Signed-off-by: Sergen Yalçın <yalcinsergen97@gmail.com>
    sergenyalcin committed Mar 19, 2024
    Configuration menu
    Copy the full SHA
    f25329f View commit details
    Browse the repository at this point in the history
  2. Add requiredFields to ignoreUnexported for fixing unit tests

    Signed-off-by: Sergen Yalçın <yalcinsergen97@gmail.com>
    sergenyalcin committed Mar 19, 2024
    Configuration menu
    Copy the full SHA
    b73a85f View commit details
    Browse the repository at this point in the history
  3. Add doc for RequiredFields function

    Signed-off-by: Sergen Yalçın <yalcinsergen97@gmail.com>
    sergenyalcin committed Mar 19, 2024
    Configuration menu
    Copy the full SHA
    845dbf6 View commit details
    Browse the repository at this point in the history