-
Notifications
You must be signed in to change notification settings - Fork 189
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
Refactor #275
Refactor #275
Conversation
Deploy preview for carbon-charts-core ready! Built with commit bb4cbec |
Deploy preview for carbon-charts-react ready! Built with commit bb4cbec |
Deploy preview for carbon-charts-angular ready! Built with commit bb4cbec https://deploy-preview-275--carbon-charts-angular.netlify.com |
Deploy preview for carbon-charts-vue ready! Built with commit bb4cbec |
Thanks @Shixie! I’d say these are all critical to make these sing which is the goal. |
Co-Authored-By: Zvonimir Fras <zvonimir.fras@gmail.com>
the specs above still have 14 as the chart title, im assuming that is a mistake |
Yes I just verified that the latest build has the correct title! 16px = correct. Thanks @natashadecoste 🙏 you are awesome. So everything in the first comment are addressed. So Mike's hoping we can get the last 3 fix addressed too, and I'm posting a check list here. Hopefully these are not too hard:
|
@shixiedesign addressed 2 out of 3 of your issues. Let's push the extra 10% space discussion either to a call/msg or our weekly cadence. There are more cases to consider there. We should address those scenarios, then the addition will be quick. With regards to the refactor, we're running behind schedule now, we should merge, and add more updates in newer PRs UPDATE: added a basic version of the 10% extra spacing, however we should still discuss in detail |
This PR should not have been merged - PRs require two developer approvals and one designer approval in addition to the submitter. Also, this is not a reviewable PR. A PR should not be closing 18 separate issues, it is impossible for there to be any effective review on that basis. |
This PR was in active review for 4 weeks. Changes were requested, applied and approved. @zvonimirfras and @cal-smith reviewed the code thoroughly, asked for changes, then approved. This was repeated multiple times. @natashadecoste also reviewed my portion, and I also reviewed her portion of the PR and asked for changes. On top of that we had @cameroncalder review from a design perspective, topped by @Shixie doing a final design review and approving. Also Mike Abbink, Sadek Bazarra and Michael Gower were shown the demos multiple times. In terms of the size of the PR, this was a massive rewrite on lots of modules. We needed this work done moving forward considering where our specifications are going. I’ve tried my best in involving everyone on the work. @alisonjoseph and @joshblack were also aware of the work. Open to suggestions in the future. |
@shinytoyrobots This PR has been actively worked on throughout June, July, August, September and October, so you may have missed your window for that kind of feedback... @theiliad Thanks for the major update, I'm looking forward to using the time series line charts! |
Great! Waiting to see how it unfolds in your project 🙂 And again (re. PR), open to any feedback/suggestions in terms of architecture, management etc moving forward. |
This is a WIP for the re-imagination of the charting components. As we make progress here I will reflect the updates in bullet point format.
Updates:
Closes #305
Closes #191
Closes #165
Closes #173
Closes #181
Closes #186
Closes #238
Closes #310
Closes #304
Closes #279
Closes #278
Closes #277
Closes #258
Closes #113
Closes #327
Closes #360
Closes #377
Closes #378