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
Note the presence of both Name and PartialName.
To a casual observer, Name implies an exact name match -- however in practice the Octopus Server treats them both as a partial match.
I.e. given a project "Integrations", Query for {Name: "gr"} will find it. This is legacy behaviour in the server, and to avoid confusion we should remove the Name field from ProjectsQuery.
As part of this work, we should sweep the library's API surface and remove any other similarly redundant fields if there are others beyond Project Name
The text was updated successfully, but these errors were encountered:
Example:
ProjectsQuery in the library has this shape:
Note the presence of both
Name
andPartialName
.To a casual observer,
Name
implies an exact name match -- however in practice the Octopus Server treats them both as a partial match.I.e. given a project "Integrations", Query for
{Name: "gr"}
will find it. This is legacy behaviour in the server, and to avoid confusion we should remove theName
field from ProjectsQuery.As part of this work, we should sweep the library's API surface and remove any other similarly redundant fields if there are others beyond Project Name
The text was updated successfully, but these errors were encountered: