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

Drop no-igd feature in favour of existing igd feature #323

Merged
merged 3 commits into from
Sep 10, 2021
Merged

Drop no-igd feature in favour of existing igd feature #323

merged 3 commits into from
Sep 10, 2021

Conversation

connec
Copy link
Contributor

@connec connec commented Sep 10, 2021

  • b5ee260 refactor!: Remove no-igd feature

    Since igd is already an optional dependency, we already have an igd
    feature which is enabled by default. To disable IGD, we can simply use
    default-features = false or --no-default-features.

    BREAKING CHANGE: The no-igd feature has been removed.

  • 1d9e38d refactor!: Make Config::port_forward depend on igd feature

    The Config struct will no longer have a port_forward field if the
    igd feature is not enabled. This removes a case where a user could set
    the config, but we would ignore it.

    BREAKING CHANGE: The port_forward field on Config is only present
    with the igd feature enabled (default).

  • a3ec0b7 ci: Run tests both with and without igd feature

    This ensures we don't accidentally release changes that won't work with
    the igd feature disabled.

Chris Connelly added 3 commits September 10, 2021 18:09
Since `igd` is already an optional dependency, we already have an `igd`
feature which is enabled by default. To disable IGD, we can simply use
`default-features = false` or `--no-default-features`.

BREAKING CHANGE: The `no-igd` feature has been removed.
The `Config` struct will no longer have a `port_forward` field if the
`igd` feature is not enabled. This removes a case where a user could set
the config, but we would ignore it.

BREAKING CHANGE: The `port_forward` field on `Config` is only present
with the `igd` feature enabled (default).
This ensures we don't accidentally release changes that won't work with
the `igd` feature disabled.
@connec connec requested a review from a team as a code owner September 10, 2021 17:16
@bochaco bochaco merged commit cdc7522 into maidsafe:master Sep 10, 2021
@connec connec deleted the yes-igd branch September 10, 2021 20:13
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.

2 participants