-
Notifications
You must be signed in to change notification settings - Fork 9
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
Remove checks for optional wildcard characters in capability and intention qualifiers #196
Labels
Milestone
Comments
k-genov
added a commit
that referenced
this issue
May 9, 2023
Obsolete features removed before 1.0.0 major release: - support for legacy heartbeat liveness, request-response subscription and intent subscription protocols - legacy notation for optional and required parameters - checks for optional wildcard characters in capability and intention qualifiers closes #196
k-genov
added a commit
that referenced
this issue
May 12, 2023
Obsolete features removed before 1.0.0 major release: - support for legacy heartbeat liveness, request-response subscription and intent subscription protocols - legacy notation for optional and required parameters - checks for optional wildcard characters in capability and intention qualifiers closes #196
danielwiehl
added a commit
that referenced
this issue
May 12, 2023
=== chore(platform): drop deprecated API and backward compatibility To prepare for `1.0.0` major release, deprecated API has been removed. - support for legacy heartbeat liveness, request-response subscription and intent subscription protocols - legacy notation for optional and required parameters - checks for optional wildcard characters in capability and intention qualifiers closes #196 BREAKING CHANGE: dropping deprecated API and backward compatibility introduced a breaking change for host and client applications. To migrate: - Update host and clients to version `1.0.0-rc.13` or higher. - Deprecated property `ManifestService.lookupApplications$` has been removed; use `ManifestService.applications` instead. - Deprecated property `Capability.requiredParams` has been removed; declare required parameters via `Capability.params` instead and mark it as required. - Deprecated property `Capability.optionalParams` has been removed; declare optional parameters via `Capability.params` instead and mark it as non-required.
danielwiehl
added a commit
that referenced
this issue
May 12, 2023
=== chore(platform): drop deprecated API and backward compatibility To prepare for `1.0.0` major release, deprecated API has been removed. - support for legacy heartbeat liveness, request-response subscription and intent subscription protocols - legacy notation for optional and required parameters - checks for optional wildcard characters in capability and intention qualifiers closes #196 BREAKING CHANGE: dropping deprecated API and backward compatibility introduced a breaking change for host and client applications. To migrate: - Update host and clients to version `1.0.0-rc.13` or higher. - Deprecated property `ManifestService.lookupApplications$` has been removed; use `ManifestService.applications` instead. - Deprecated property `Capability.requiredParams` has been removed; declare required parameters via `Capability.params` instead and mark it as required. - Deprecated property `Capability.optionalParams` has been removed; declare optional parameters via `Capability.params` instead and mark it as non-required.
danielwiehl
added a commit
that referenced
this issue
May 12, 2023
=== chore(platform): drop deprecated API and backward compatibility To prepare for `1.0.0` major release, deprecated API has been removed. - support for legacy heartbeat liveness, request-response subscription and intent subscription protocols - legacy notation for optional and required parameters - checks for optional wildcard characters in capability and intention qualifiers closes #196 BREAKING CHANGE: dropping deprecated API and backward compatibility introduced a breaking change for host and client applications. To migrate: - Update host and clients to version `1.0.0-rc.13` or higher. - Deprecated property `ManifestService.lookupApplications$` has been removed; use `ManifestService.applications` instead. - Deprecated property `Capability.requiredParams` has been removed; declare required parameters via `Capability.params` instead and mark it as required. - Deprecated property `Capability.optionalParams` has been removed; declare optional parameters via `Capability.params` instead and mark it as non-required.
danielwiehl
added a commit
that referenced
this issue
May 12, 2023
=== chore(platform): drop deprecated API and backward compatibility To prepare for `1.0.0` major release, deprecated API has been removed. - support for legacy heartbeat liveness, request-response subscription and intent subscription protocols - legacy notation for optional and required parameters - checks for optional wildcard characters in capability and intention qualifiers closes #196 BREAKING CHANGE: dropping deprecated API and backward compatibility introduced a breaking change for host and client applications. To migrate: - Update host and clients to version `1.0.0-rc.13` or higher. - Deprecated property `ManifestService.lookupApplications$` has been removed; use `ManifestService.applications` instead. - Deprecated property `Capability.requiredParams` has been removed; declare required parameters via `Capability.params` instead and mark it as required. - Deprecated property `Capability.optionalParams` has been removed; declare optional parameters via `Capability.params` instead and mark it as non-required.
danielwiehl
added a commit
that referenced
this issue
May 12, 2023
=== chore(platform): drop deprecated API and backward compatibility To prepare for `1.0.0` major release, deprecated API has been removed. - support for legacy heartbeat liveness, request-response subscription and intent subscription protocols - legacy notation for optional and required parameters - checks for optional wildcard characters in capability and intention qualifiers closes #196 BREAKING CHANGE: dropping deprecated API and backward compatibility introduced a breaking change for host and client applications. To migrate: - Update host and clients to version `1.0.0-rc.13` or higher. - Deprecated property `ManifestService.lookupApplications$` has been removed; use `ManifestService.applications` instead. - Deprecated property `Capability.requiredParams` has been removed; declare required parameters via `Capability.params` instead and mark it as required. - Deprecated property `Capability.optionalParams` has been removed; declare optional parameters via `Capability.params` instead and mark it as non-required.
danielwiehl
added a commit
that referenced
this issue
May 12, 2023
=== chore(platform): drop deprecated API and backward compatibility To prepare for `1.0.0` major release, deprecated API has been removed. - support for legacy heartbeat liveness, request-response subscription and intent subscription protocols - legacy notation for optional and required parameters - checks for optional wildcard characters in capability and intention qualifiers closes #196 BREAKING CHANGE: dropping deprecated API and backward compatibility introduced a breaking change for host and client applications. To migrate: - Update host and clients to version `1.0.0-rc.13` or higher. - Deprecated property `ManifestService.lookupApplications$` has been removed; use `ManifestService.applications` instead. - Deprecated property `Capability.requiredParams` has been removed; declare required parameters via `Capability.params` instead and mark it as required. - Deprecated property `Capability.optionalParams` has been removed; declare optional parameters via `Capability.params` instead and mark it as non-required.
danielwiehl
added a commit
that referenced
this issue
May 12, 2023
=== chore(platform): drop deprecated API and backward compatibility To prepare for `1.0.0` major release, deprecated API has been removed. - support for legacy heartbeat liveness, request-response subscription and intent subscription protocols - legacy notation for optional and required parameters - checks for optional wildcard characters in capability and intention qualifiers closes #196 BREAKING CHANGE: dropping deprecated API and backward compatibility introduced a breaking change for host and client applications. To migrate: - Update host and clients to version `1.0.0-rc.13` or higher. - Deprecated property `ManifestService.lookupApplications$` has been removed; use `ManifestService.applications` instead. - Deprecated property `Capability.requiredParams` has been removed; declare required parameters via `Capability.params` instead and mark it as required. - Deprecated property `Capability.optionalParams` has been removed; declare optional parameters via `Capability.params` instead and mark it as non-required.
danielwiehl
added a commit
that referenced
this issue
May 12, 2023
=== chore(platform): drop deprecated API and backward compatibility To prepare for `1.0.0` major release, deprecated API has been removed. - support for legacy heartbeat liveness, request-response subscription and intent subscription protocols - legacy notation for optional and required parameters - checks for optional wildcard characters in capability and intention qualifiers closes #196 BREAKING CHANGE: dropping deprecated API and backward compatibility introduced a breaking change for host and client applications. To migrate: - Update host and clients to version `1.0.0-rc.13` or higher. - Deprecated property `ManifestService.lookupApplications$` has been removed; use `ManifestService.applications` instead. - Deprecated property `Capability.requiredParams` has been removed; declare required parameters via `Capability.params` instead and mark it as required. - Deprecated property `Capability.optionalParams` has been removed; declare optional parameters via `Capability.params` instead and mark it as non-required.
k-genov
added a commit
that referenced
this issue
May 15, 2023
To prepare for `1.0.0` major release, deprecated API has been removed. - support for legacy heartbeat liveness, request-response subscription and intent subscription protocols - legacy notation for optional and required parameters - checks for optional wildcard characters in capability and intention qualifiers closes #196 BREAKING CHANGE: dropping deprecated API and backward compatibility introduced a breaking change for host and client applications. To migrate: - Update host and clients to version `1.0.0-rc.13` or higher. - Deprecated property `ManifestService.lookupApplications$` has been removed; use `ManifestService.applications` instead. - Deprecated property `Capability.requiredParams` has been removed; declare required parameters via `Capability.params` instead and mark it as required. - Deprecated property `Capability.optionalParams` has been removed; declare optional parameters via `Capability.params` instead and mark it as non-required.
k-genov
added a commit
that referenced
this issue
May 15, 2023
To prepare for `1.0.0` major release, deprecated API has been removed. - support for legacy heartbeat liveness, request-response subscription and intent subscription protocols - legacy notation for optional and required parameters - checks for optional wildcard characters in capability and intention qualifiers closes #196 BREAKING CHANGE: dropping deprecated API and backward compatibility introduced a breaking change for host and client applications. To migrate: - Update host and clients to version `1.0.0-rc.13` or higher. - Deprecated property `ManifestService.lookupApplications$` has been removed; use `ManifestService.applications` instead. - Deprecated property `Capability.requiredParams` has been removed; declare required parameters via `Capability.params` instead and mark it as required. - Deprecated property `Capability.optionalParams` has been removed; declare optional parameters via `Capability.params` instead and mark it as non-required.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the user tries to register a capability or an intention containing the unsupported optional wildcard, an error is thrown.
In a future release, no error should be thrown anymore.
Search for this issue in the code in order to remove the corresponding blocks.
The text was updated successfully, but these errors were encountered: