Skip to content

Expose logic for creating new team configs/schemas #3088

@traeok

Description

@traeok

Is your feature request related to a problem? Please describe.

From the perspective of a Zowe Explorer extender, I would have to re-implement most of the logic for creating a new team config and schema. This would likely involve duplicating code that already exists in Zowe Explorer's codebase in order to access it.

Describe the solution you'd like

It would be helpful to provide some of this logic in ZE API, if possible, to avoid code duplication and to allow this feature to be leveraged by extenders.

Describe alternatives you've considered

Copy/pasting the code from Zowe Explorer itself, but this feels redundant and is not easy to maintain.

Additional context

Follow up on discussion in issue #3078

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestpriority-highProduction outage - this quarter or at least next quarter

Type

No type
No fields configured for issues without a type.

Projects

Status
Closed

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions