Skip to content

Enable local compare targets automatically in Development environment #62

@georgidhristov

Description

@georgidhristov

Description

DebugProbe currently requires manual configuration to allow local compare targets:

options.AllowLocalCompareTargets = true;

This creates unnecessary setup during local development where compare functionality is commonly used.

Current Behavior

AllowLocalCompareTargets defaults to false in all environments unless explicitly configured by the user.

Expected Behavior

DebugProbe should automatically enable local compare targets when the application runs in the Development environment.

Behavior should work as follows:

  • Development

    • default value should be true
  • all other environments

    • default value should remain false

Important

If the user explicitly configures the option:

options.AllowLocalCompareTargets = true;

or

options.AllowLocalCompareTargets = false;

that value should always take priority over automatic environment-based defaults.

Suggested Fix

Inside the DebugProbe configuration/setup logic:

  • detect the current hosting environment
  • automatically enable local compare targets for Development
  • preserve explicit user configuration when provided

Result

After this change:

  • local compare setup becomes easier during development
  • safer defaults remain for non-development environments
  • explicit user configuration is preserved
  • developer experience improves with less manual configuration

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions