-
Notifications
You must be signed in to change notification settings - Fork 486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate API Documents #748
Conversation
Pull Request Test Coverage Report for Build 555
💛 - Coveralls |
701d212
to
27c3d12
Compare
Hey @matuzalemsteles, I'm getting the How can I test it in the meantime? |
Hey @jbalsas, I'm expecting the release of Electric, but to work temporarily I'm modifying in |
e5f4ffd
to
8143b42
Compare
Hey @jbalsas, I just updated with the latest release of Electric, it looks ready to go now. |
Hey @matuzalemsteles, I'm getting the following error when trying to build the site:
Also... it took about 5 minutes to fail... is this missing anything? |
@jbalsas, This error is because of issue #740, the first moment seemed to be an error coming from Electric, but I tried rendering other Clay components and seems to work fine then it can be a problem inside ClayCharts ... It has to be investigated. On the delay this is real, Electric is taking too long to render the components in html and ends up being annoying, because every time we update something it always renders the API again and a few more long minutes to wait. Maybe I'm wrong and it could be because of the mistakes... Edit: Soon after the error stopped the console? |
So, what should I do to test this? Can we fix that? How are you testing it? |
I'm just running I am investigating this error at the moment, |
Hey @jbalsas, now we can continue with this 🙂. Electric calls the |
Hey @matuzalemsteles For me all lifecycle inherited methods should be called. Maybe right now In fact I think is a good practice we should follow on every component. Your thoughts @jbalsas ? :) |
Yeah, all lifecyle should be called. There's likely something wrong in |
Hey @jbalsas @carloslancha, That sounds good to me, I'll reverse this. I've been analyzing, the ChartBase TypeError: (intermediate value).disposed is not a function As the webpack transpiles the _get(_obj.__proto__ || Object.getPrototypeOf(_obj), 'disposed', this).call(this); So I'm just adding ChartBase visibility to DataComponent. @jbalsas What do you think? |
Hey @matuzalemsteles, why would this be needed in |
Hey @jbalsas, Because Electric uses the The same error is given when we give a |
Hey @matuzalemsteles, yeah, I can see that, but since it is extending @julien, we need to add some tests to charts to at least test that the |
@jbalsas, @matuzalemsteles sorry, I didn't receive any notification from GitHub yesterday which is why I didn't reply yet. I just fetched the
Which is probably due to this @jbalsas Ok, I'll add some tests to check that everything works as expected with the component's @matuzalemsteles in the meantime, if you need to make any changes or need some help, feel free to ping me. |
@jbalsas and @matuzalemsteles I removed I also added various |
@julien Thanks for the answer. Hey @jbalsas, I've been giving it a lookup, and
|
Yeah, that makes sense... can you open an issue so we figure out how to better structure the charts hierarchy? I'm trying this without the changes on top of |
Works like a charm, @matuzalemsteles!! Nice job! 👍 |
Thanks. Okay, I can work on this later. |
Hey @jbalsas, For this PR to be able to move on, it's depending on the pr liferay/electric#139 on the Electric for it to work again.
New
Disclaimer
The problem of compiling with the Charts components on clayui.com seems to be a particular problem, I've tested it with other components and it seems to work fine, we have to dig deeper to know what it's causing.
The API page is separate from the list of components, this is a bit poor in navigation between the component pages and the API, we can think of adding a
topbar
to improve navigation and user experience.The design of the page is very simple, I tried to follow what we see in the
alloy-editor
feel free to modify later, I think we can improve still.