You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At present, a CDI device specification is considered invalid when it contains no container edits, however, since the union of top-level spec conainerEdits and device-level containerEdits are applied to a container, we could relax this restriction to consider a device valid as long as the union of edits is non-empty.
The text was updated successfully, but these errors were encountered:
Hi @cyclinder we're still discussing whether this is something that we want to include in the spec. You're welcome to have a look at it already, but keep in mind that we might decide to not go this way.
This issue is stale because it has been open 90 days with no activity. This issue will be closed in 30 days unless new comments are made or the stale label is removed. To skip these checks, apply the "lifecycle/frozen" label.
Uh oh!
There was an error while loading. Please reload this page.
At present, a CDI device specification is considered invalid when it contains no container edits, however, since the union of top-level spec
conainerEdits
and device-levelcontainerEdits
are applied to a container, we could relax this restriction to consider a device valid as long as the union of edits is non-empty.The text was updated successfully, but these errors were encountered: