When to start gitgraph-angular

Hey,

Don’t know if you remember me, but I was interested in creating gitgraph-angular. I have a fair amount of Angular experience

Is there a workable gitgraph API to use at the moment, or should I wait?

Let me know

Thanks!

[nicoespeon]

@dolanmiu yeah, basically this is just JavaScript. You can see JSX as syntactic sugar so it looks-like HTML, but it’s all JS.

Concerning the philosophy of the rendering lib, the idea is the following:

• you provide a component (“module” if I correctly remind Angular) that instantiate the Gitgraph Core
• the component provide the gitgraph instance
• user of the component can use gitgraph API to do whatever he wants to
• the component is responsible of rendering the result of gitgraph modifications

As for change detection, you can do that with what Fabien gave you: https://github.com/nicoespeon/gitgraph.js/blob/faedd32e5f309f9bfbf6ff2e39b13e9bf18119e2/packages/gitgraph-react/src/Gitgraph.tsx#L42

Basically, you can subscribe to gitgraph and you’ll be notified whenever a change happens that needs to be rendered. In React, we do update the state, which re-render our component.

[nicoespeon]

Hi @dolanmiu 👋

You can create a branch from the 2.0.0 branch. You have the gitgraph-core lib in it, along rendering packages (one POC in Node.js, the other in React). Here you can create a gitgraph-angular to implement rendering in an Angular component.

I’d say the core is not completely stable (some features are still missing + we may change the API a bit if we find opportunities to do so), but it’s complete enough to start working on it and implement a couple of scenarios already.

cc @fabien0102 what do you think?