Skip to content
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 for SignalManager changes #277

Merged

Conversation

williamsyang-work
Copy link
Contributor

Replaces Signal keys with strings for event handlers Replaces fire* methods with emit methods

@williamsyang-work
Copy link
Contributor Author

williamsyang-work commented Oct 31, 2024

@ngondalia I'd like to know if the new typing inside ExternalAPI passes the type-enforcement into downstream repos. LMK how it works!

this.handleUpdatedProperties(emptyPayload);
}
handleExperimentChanged = (exp?: Experiment) => {
const payload = exp ? this.propertiesMap.get(exp.UUID) : new ItemPropertiesSignalPayload({});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am getting 'TypeError: Cannot read properties of undefined (reading 'getExperimentUUID')'

The payload could be undefined here - Either have to address it here or could handle it in handleUpdatedProperties

Copy link
Contributor Author

@williamsyang-work williamsyang-work Nov 1, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yea, there was a weird issue where when exp is Experiment | undfined you can't pass string | undefined into the getter. So i changed the logic but made the assumption we would always find something if exp was defined..

Anyway... I added another checker so if this.propertiesMap.get(exp.UUID) doesn't find anything we just put an empty ItemPropertiesSignalPayload which should fix that.

@bhufmann
Copy link
Collaborator

bhufmann commented Nov 26, 2024

@williamsyang-work could you please rebase this PR and fix the linter issues. There is a merge conflict with a recent change. Meanwhile I re-review the corresponding theia-trace-extension PR.

@williamsyang-work
Copy link
Contributor Author

@williamsyang-work could you please rebase this PR and fix the linter issues. There is a merge conflict with a recent change. Meanwhile I re-review the corresponding theia-trace-extension PR.

Sure. I had this as a draft until the theia-extension PR was merged. I will tidy this one up for proper review.

Replaces Signal keys with strings for event handlers
Replaces fire* methods with emit methods

Signed-off-by: Will Yang <[email protected]>
Copy link
Collaborator

@bhufmann bhufmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The trace-viewer components have been released with version v0.5.0. (eclipse-cdt-cloud/theia-trace-extension#1159). Please update this PR to upgrade to that version. Rrefer also #288 to see which files to update for the upgrade.

@williamsyang-work williamsyang-work marked this pull request as ready for review December 3, 2024 17:33
@bhufmann
Copy link
Collaborator

bhufmann commented Dec 3, 2024

The following IP tickets have been created for the upgrade to traceviewer components v0.5.0:

@bhufmann bhufmann requested a review from ngondalia December 3, 2024 20:59
Copy link
Collaborator

@bhufmann bhufmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks good to me. Thanks!

Copy link
Collaborator

@bhufmann bhufmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just realized that the README.md is describing the external API and it needs to be updated. Please go through the following chapter and update it the new API. The API is shown there and there is an example for the experiment selected signal as far I can see.

https://github.com/eclipse-cdt-cloud/vscode-trace-extension/blob/master/README.md#using-the-external-api

Copy link
Collaborator

@bhufmann bhufmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Thanks!

@marcdumais-work marcdumais-work requested review from marcdumais-work and removed request for ngondalia December 4, 2024 21:04
@marcdumais-work
Copy link
Contributor

There's an extra dependency requiring an IP Ticket that popped-up (it was not mentioned in the previous CI run):

image

IP ticket:
https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/17767

Copy link
Contributor

@marcdumais-work marcdumais-work left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Really nice contribution @williamsyang-work! (specially when considering the related ground work you first did in the theia-trace-extension repo)

@marcdumais-work
Copy link
Contributor

marcdumais-work commented Dec 6, 2024

There's an extra dependency requiring an IP Ticket that popped-up (it was not mentioned in the previous CI run):

IP ticket: https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/17767

I do not think we need for this ticket to be resolved before merging - I had a look and I am 99.9% sure this License check failure is a false positive.

@bhufmann
Copy link
Collaborator

bhufmann commented Dec 9, 2024

I'm going to merge this change. Then, I plan to do a release this week. @ngondalia please let me know if you have any concern about the release.

@bhufmann bhufmann merged commit 165ac11 into eclipse-cdt-cloud:master Dec 9, 2024
5 of 6 checks passed
@marcdumais-work
Copy link
Contributor

There's an extra dependency requiring an IP Ticket that popped-up (it was not mentioned in the previous CI run):
IP ticket: https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/17767

IP Ticket closed (approved)

@ngondalia
Copy link
Contributor

I'm going to merge this change. Then, I plan to do a release this week. @ngondalia please let me know if you have any concern about the release.

Thanks for the heads up! I will do sanity testing on our end and will get back to you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants