Shape Up đŸ‹ïžâ€â™€ïž

Visualize the progress we're making, one cycle at a time. Don't know what Shape Up is about? Learn more.

This cycle started on Mon Mar 15 2021 and finished on Mon Apr 26 2021.

Attention

This cycle has already finished.Go to the current cycle.

Figuring things outMaking it happen

History

Jonas Lagoni
Updated progress of
Define Parser(s) API
to 100% ✹ on Mon Apr 26 2021
Sergio Moya
Updated progress of
Define Parser(s) API
to 100% ✹ on Fri Apr 23 2021

Parser API v1.0.0-alpha got documented: https://github.com/asyncapi/parser-api 🎉 🎉 🎉 🎉

Sergio Moya
Updated progress of
Define Parser(s) API
to 95% on Thu Apr 22 2021

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.

Sergio Moya
Updated progress of
Define Parser(s) API
to 90% on Wed Apr 21 2021

We updated the documentation of the new Intent-driven API and added all missing intents.

Sergio Moya
Updated progress of
Define Parser(s) API
to 75% on Tue Apr 20 2021

We have been added new intents to the API documentation so we cover all the use cases we consider validated.

Sergio Moya
Updated progress of
Define Parser(s) API
to 70% on Thu Apr 15 2021

New API validated against markdown-template. Diff of changes to adapt it to the new Parser API can be found here

Jonas Lagoni
Updated progress of
Define Parser(s) API
to 60% on Tue Apr 06 2021

we have defined the mock intent API and started integrating it with tools to validate the API holds up.

Sergio Moya
Updated progress of
Define Parser(s) API
to 40% on Fri Mar 26 2021

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.

Sergio Moya
Updated progress of
Define Parser(s) API
to 25% on Tue Mar 23 2021

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.

Sergio Moya
Updated progress of
Define Parser(s) API
to 10% on Fri Mar 19 2021

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.

Jonas Lagoni
Updated progress of
Identify library parser API intents
to 100% ✹ on Wed Mar 17 2021
Jonas Lagoni
Updated progress of
Identify library parser API intents
to 100% ✹ on Wed Mar 17 2021

defined intent for different use-cases, which should suffice in continuing to the next stage

Sergio Moya
Updated progress of
Identify library parser API intents
to 25% on Tue Mar 16 2021

We started listing the intents we can find in https://github.com/asyncapi/ts-nats-template repo.