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
feat(docs-infra): created new widget for events page #36517
Conversation
@petebacondarwin @StephenFluin @gkalpak if we can finalize the way in which the new events widget will be implemented after that I will add tests |
You can preview bf62aab at https://pr36517-bf62aab.ngbuilds.io/. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've wanted this for a long time, thx, @ajitsinghkaler 🎉
I've left a first round of comments.
You can preview 5332c91 at https://pr36517-5332c91.ngbuilds.io/. |
@gkalpak made the changes but made the event data changes only on few events once we confirm it we can migrate the whole data |
You can preview 171f7c0 at https://pr36517-171f7c0.ngbuilds.io/. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thx for making the changes, @ajitsinghkaler 🚀
Here's a second round of comments 😁
Happy to let @gkalpak take the lead on reviewing this. If you want extra input from me, please re-add me as a reviewer when it is ready. |
You can preview b473d7b at https://pr36517-b473d7b.ngbuilds.io/. |
@gkalpak made the changes please have a look |
You can preview 8d3bd94 at https://pr36517-8d3bd94.ngbuilds.io/. |
I will make linting changes later |
@ajitsinghkaler, could you rebase this and fix conflicts? |
Data in events page was hardcoded and it is manually moved in the table. Created a new events widget which will automatically move past and upcoming events from events.json (`aio/content/marketing/events.json`) file to the relevant table in the events tab
In the events.json file most of tooltips are same as name so there were of no use, as they were providing no extra information. So, removed them from the events.json file
…cases This commit simplifies the tests of `EventsComponent` (by introducing a `createMockEvent()` helper and getting rid of the irrelevant `Event` fields) and adds tests for some more usecases. It also makes the tests more robust by using Jasmine's `Clock` to mock the current date.
647476a
to
d73cfd2
Compare
You can preview d73cfd2 at https://pr36517-d73cfd2.ngbuilds.io/. |
@gkalpak rebased it tell me anything else needed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed-for: global-docs-approvers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thank you!
Reviewed-for: global-approvers, size-tracking
In the events.json file most of tooltips are same as name so there were of no use, as they were providing no extra information. So, removed them from the events.json file PR Close #36517
…cases (#36517) This commit simplifies the tests of `EventsComponent` (by introducing a `createMockEvent()` helper and getting rid of the irrelevant `Event` fields) and adds tests for some more usecases. It also makes the tests more robust by using Jasmine's `Clock` to mock the current date. PR Close #36517
Data in events page was hardcoded and it is manually moved in the table. Created a new events widget which will automatically move past and upcoming events from events.json (`aio/content/marketing/events.json`) file to the relevant table in the events tab PR Close #36517
In the events.json file most of tooltips are same as name so there were of no use, as they were providing no extra information. So, removed them from the events.json file PR Close #36517
…cases (#36517) This commit simplifies the tests of `EventsComponent` (by introducing a `createMockEvent()` helper and getting rid of the irrelevant `Event` fields) and adds tests for some more usecases. It also makes the tests more robust by using Jasmine's `Clock` to mock the current date. PR Close #36517
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Data has to be manually changed in events
Issue Number: N/A
What is the new behavior?
Data will automatically be changed in presented and upcoming events
Does this PR introduce a breaking change?
Other information