Visualize the progress we're making, one cycle at a time. Don't know what Shape Up is about? Learn more.
Ideas we're now committed to implement during this 6 weeks cycle.
Scopes are groups of related tasks.
This cycle started on Mon Mar 15 2021 and finished on Mon Apr 26 2021.
This cycle has already finished.Go to the current cycle.
Parser API v1.0.0-alpha got documented: https://github.com/asyncapi/parser-api 🎉 🎉 🎉 🎉
conclusions reached. As mentioned in https://github.com/asyncapi/parser-api/pull/1/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R26, each parser repository will maintain its compatibility matrix.
We have created a new repository that will contain the new Parser(s) API. There is a PR on it with the new intent-driven API specification and some design documents: https://github.com/asyncapi/parser-api/pull/1
We wrote down some options to consider. A discussion has been started around and we are trying to reach an agreement.
We updated the documentation of the new Intent-driven API and added all missing intents.
We have been added new intents to the API documentation so we cover all the use cases we consider validated.
New API validated against markdown-template. Diff of changes to adapt it to the new Parser API can be found here
we have defined the mock intent API and started integrating it with tools to validate the API holds up.
We have created a PR that contains a draft of the Parser API. However, the suggested API is not as resilient to breaking changes as we desired. @jonaslagoni applied the emulated breaking changes from shape-up-process/issues/93 and figured out some issues we may face. See the test results here.
We have been sharing different approaches and it seems we have one that can be used as base:
However, several good points were made on https://github.com/asyncapi/shape-up-process/issues/90#issuecomment-804845905 and we are waiting for another pass by @jonaslagoni based on the intents we recap in https://github.com/asyncapi/shape-up-process/issues/84. This will be useful for validating the suggestion.
Emulated 2 new breaking changes. One based on https://github.com/asyncapi/shape-up-process/issues/73 and another one based on https://github.com/asyncapi/parser-js/issues/210.
We have been looking for different API approaches and added a couple of suggestions. We are looking for setting the API foundation based on intents.
Emulated breaking change based on https://github.com/asyncapi/spec/issues/434
Emulated breaking change based on https://github.com/asyncapi/shape-up-process/issues/73
defined intent for different use-cases, which should suffice in continuing to the next stage
We started listing the intents we can find in https://github.com/asyncapi/ts-nats-template repo.