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

Failed messages to typescript #1769

Merged
merged 68 commits into from
Mar 14, 2024
Merged

Failed messages to typescript #1769

merged 68 commits into from
Mar 14, 2024

Conversation

cquirosj
Copy link
Contributor

@cquirosj cquirosj commented Mar 5, 2024

Migrated all components in the failed messages area to TypeScript and remedy multiple minor issues in this area

@cquirosj cquirosj force-pushed the failed-messages-to-vue branch from b751e09 to 136864b Compare March 5, 2024 23:42
mikeminutillo and others added 4 commits March 6, 2024 18:08
Will probably need to move MessageHeader interface to a separate file and may need to break it up into multiple types
Copy link
Member

@johnsimons johnsimons left a comment

Choose a reason for hiding this comment

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

A few comments so far

PhilBastian and others added 9 commits March 7, 2024 14:30
…etedMessages.vue

Co-authored-by: Phil Bastian <155411597+PhilBastian@users.noreply.github.com>
…nOperations.vue

Co-authored-by: Phil Bastian <155411597+PhilBastian@users.noreply.github.com>
…eView.vue

Co-authored-by: Phil Bastian <155411597+PhilBastian@users.noreply.github.com>
* Convert EditRetryDialog to Typescript

* Add the optional chaining operator back into the template

* Update emit to typescript

* Fixing errors after rebase

* Update src/ServicePulse.Host/vue/src/components/failedmessages/EditRetryDialog.vue

Co-authored-by: John Simons <john.simons@particular.net>

* fixing v-for loop

---------

Co-authored-by: Christian <christian.quiros+github@gmail.com>
Co-authored-by: Christian <christian.quiros@particular.net>
Co-authored-by: John Simons <john.simons@particular.net>
@cquirosj
Copy link
Contributor Author

@cquirosj As part of this PR, there should not be a need to modify either vite.config.ts or tsconfig.*.ts at all, are there any issues you are having building the project?

All changes made to config.ts files have been reverted.

const response = await useFetchFromServiceControl(`archive/groups/id/${groupId}`);
const data = await response.json();
async function loadGroupDetails(groupId: string) {
const [, data] = await useTypedFetchFromServiceControl<FailureGroup>(`archive/groups/id/${groupId}`);
Copy link
Member

Choose a reason for hiding this comment

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

Unfortunately it may be too late, but it would be nice for all the URLs to be typed from routeLinks

@cquirosj cquirosj marked this pull request as ready for review March 14, 2024 01:35
@PhilBastian PhilBastian requested a review from johnsimons March 14, 2024 01:44
@cquirosj cquirosj merged commit 0b0ff37 into master Mar 14, 2024
5 checks passed
@cquirosj cquirosj deleted the failed-messages-to-vue branch March 14, 2024 02:03
@cquirosj cquirosj modified the milestones: vNext, 1.38.2 Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Refactoring Type: Refactoring
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants