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.
{{ message }}
This repository has been archived by the owner on Mar 11, 2021. It is now read-only.
As a developer, I want to have a stable development and deployment environment for the library version of the Planner component.
Functional Acceptance Criteria
The Planner can be built as an integration library/component that can be used by external Angular 2 applications.
Non-functional Acceptance Criteria
There is an easy to setup and use way to code-iterate over the Planner.
Note: This story is more about the non-functional criterias. The library build/deployment needs an easy way for developers to do development cycles without dealing with a complex setup. This might be a setup with the platform project running locally, but could also be something like a generic minimal frame, omitting the platform for development of the Planner. So this story will boil down on looking how development is working with the Platform-Planner setup.
The text was updated successfully, but these errors were encountered:
Description
As a developer, I want to have a stable development and deployment environment for the library version of the Planner component.
Functional Acceptance Criteria
Non-functional Acceptance Criteria
Note: This story is more about the non-functional criterias. The library build/deployment needs an easy way for developers to do development cycles without dealing with a complex setup. This might be a setup with the platform project running locally, but could also be something like a generic minimal frame, omitting the platform for development of the Planner. So this story will boil down on looking how development is working with the Platform-Planner setup.
The text was updated successfully, but these errors were encountered: