Drop no-igd
feature in favour of existing igd
feature
#323
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
b5ee260 refactor!: Remove
no-igd
featureSince
igd
is already an optional dependency, we already have anigd
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 onigd
featureThe
Config
struct will no longer have aport_forward
field if theigd
feature is not enabled. This removes a case where a user could setthe config, but we would ignore it.
BREAKING CHANGE: The
port_forward
field onConfig
is only presentwith the
igd
feature enabled (default).a3ec0b7 ci: Run tests both with and without
igd
featureThis ensures we don't accidentally release changes that won't work with
the
igd
feature disabled.