Skip to content

feat(misconf): Better default values for scan types #9341

Description

@simar7

Should we rethink the .AsStringValueOrDefault() approach? The reason I say it is because if it's not set the default will be the empty value "".

Would using a "known" placeholder be better than an empty value like ""? For instance, that would eliminate the issue where a value is mistakenly forgotten to be set vs. actually being empty due to a bug.

Originally posted by @simar7 in #9296 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Fields

    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions