Ideas we're now committed to implement during this 6 weeks cycle.
Scopes are groups of related tasks.
The current cycle started on Mon Mar 15 2021 and will finish on Mon Apr 26 2021.
Waiting for review and for merging this PR.
I wrote "stringify" function inside this PR. At the moment task is waiting for publishing "new" components with unified styling.
umd bundle and it works. Waiting for https://github.com/asyncapi/shape-up-process/issues/105 and https://github.com/asyncapi/shape-up-process/issues/86 tasks to go forward.
Render side menu/navigation and missed examples for messages. Everything was added from HTML-Template. The skipped items will be added along with the https://github.com/asyncapi/shape-up-process/issues/86
As suggested by Fran, I switched from server-side parsing to client-side parsing and I have this same problem like described here, so first I must fix problem in React component side to go further.
In asyncapi/html-template#166 there is still work to be done:
I also want to try generate the page with Gatsby (suggested by Łukasz) and see if it reduces the template size.
"New" component supports in every place parser API. PR with removing
Currently, the component supports everything that has been mentioned. The only thing that still needs to be added to component is the side menu/navigation.
In asyncapi/asyncapi-react#280 PR:
Info component uses TailwindCSS - commit
In asyncapi/asyncapi-react#276 PR:
New component for Schema (in PR) already uses
parser-js API. After adapting components that use the old
Schema component, the
beautify stage will be removed and the task will be marked as completed.
Start using TailwindCSS in react-component. First PR: https://github.com/asyncapi/asyncapi-react/pull/269
Create draft PR to show how we can integrate React component inside HTML template - https://github.com/asyncapi/html-template/pull/166
Create draft PR to show how we can integrate React component - https://github.com/asyncapi/studio/pull/17
I think that separate route
/parse on backend should parse AsyncAPI spec from Editor and only in component we should consume parsed spec - parsing in backend is faster than in client and also client is much more light (in this situation, we don't need parser on client side).
Open PR - https://github.com/asyncapi/asyncapi-react/pull/264 Changes will be merged to
I figured out how we can render component in HTML-template:
web-component. We can save bundled js files from web-component (from here) as js files in template and "serve" them. Problem is that it's not a true SSR so SEO will be worse (as I know only google can index SPA application).
hydration. First we will show "stringified" component by
ReactDOMServer.renderToString function and then hydrate it by
React.hydrate function. For that we need at least react component saved in single file in
umd format, so at the moment this is a problem - we must add webpack or rollup to react component, and bundling before publishing to npm to different formats: esm, cjs, umd.
Render component like Gatsby renders page - similar to 2. point, but Gatsby bundle hydration and stringified in one process. I don't know how to do that, but I will spend some time on it, if I will have on end of cycle, because for me this is a best way to handle rendering the component.
Starting task. First, I want to check if the current react component can be rendered as template. I'll give myself one day for it. It's only a premature-integration. Then I will start other tasks.
Info, Servers, Channels, Messages are using
parser-js api. I left Schemas, because this part should be rewritten to meet the requirements of the task https://github.com/asyncapi/shape-up-process/issues/86
Info and Servers components are using