Skip to content

Refactor/ab#82357 update angular fix memory leak issues and other fixes #2430

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

Open
wants to merge 20 commits into
base: beta
Choose a base branch
from

Conversation

unai-reliefapp
Copy link
Contributor

@unai-reliefapp unai-reliefapp commented Mar 4, 2024

Description

Fixed, among other minor issues:

  • fix most of the memory issues for unsubscribed values(some subscriptions are added on root services and cannot be unsubscribed until the app is closed) including unsubscribe flag for all widget settings forms, add missing subscription tear down for some observables
  • refactor many subscriptions within subscriptions to a single subscribe method in order to keep the code simple, effective and readable
  • fix all timeout listeners missing proper clear functions
  • fix required control label update from form wrapper when no label is set in the html
  • fix proper message sent on notification create/update/delete(duplication of same message and success message was send even if request failed)
  • fix correct role list fetch on list inside application and duplicate display message for add/delete role(duplication of same message and success message was send even if request failed)
  • fix property updates for resource and resources type questions in form builder, including search and add record button and table display and table buttons for resources

Useful links

Type of change

Please delete options that are not relevant.

  • Improvement (refactor or addition to existing functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

  • Test A
  • Test B

Screenshots

Please include screenshots of this change. If this issue is only back-end related, and does not involve any visual change of the platform, you can skip this part.

Checklist:

( * == Mandatory )

  • * I have set myself as assignee of the pull request
  • * My code follows the style guidelines of this project
  • * Linting does not generate new warnings
  • * I have performed a self-review of my own code
  • * I have put the ticket for review, adding the oort-frontend team to the list of reviewers
  • * I have commented my code, particularly in hard-to-understand areas
  • * I have put JSDoc comment in all required places
  • * My changes generate no new warnings
  • * I have included screenshots describing my changes if relevant
  • * I have selected labels in the Pull Request, according to the changes with code brings
  • I have made corresponding changes to the documentation ( if required )
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

More explanation

https://www.loom.com/share/05a716d61b9744faaf51fb304c21d1e5?sid=f87cf896-582a-4f76-93ae-8ceed801b145

AntoineRelief and others added 15 commits December 19, 2023 10:41
…ain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
* feat: Update kendo packages  to v14 (#2212)

---------

Co-authored-by: Antoine Hurard <[email protected]>

---------

Co-authored-by: Antoine Hurard <[email protected]>
Co-authored-by: Estela Ferreira <[email protected]>
…ain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
…lain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
…lain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
…es fix: add missing subscription teardown logic part 1
@unai-reliefapp unai-reliefapp added keep Do not delete refactor Refactor of the code in code review Under review labels Mar 4, 2024
@unai-reliefapp unai-reliefapp self-assigned this Mar 4, 2024
…es refactor: inner subscription in order to keep single subscription in all involved observables for back-office app fix: add missing unsubscription logic
…es refactor: inner subscription in order to keep single subscription in all involved observables for front-office and web-components and app and rest of libraries fix: add missing unsubscription logic
@unai-reliefapp unai-reliefapp force-pushed the refactor/AB#82357_update-angular-fix-memory-leak-issues-and-other-fixes branch from 363920d to c24824d Compare March 5, 2024 16:01
…es feat: add unsubscription logic for all setttings form with value changes subscription refactor: remove some unnecessary pipes for graphql queries and mutations fix: required control label update from form wrapper when no label is set in the html
…es fix: notification snackbar messages and callback trigger on success and error, as success message was always set even with errors, so add success snackbar to callback method feat: update notification methods to trigger snackbar messages from the related service fix: group list translations plus refactor some methods to remove subscriptions within subscriptions fix: all role list load when add/remove/edit one inside an application, plus refactor some methods to remove subscriptions within subscriptions
…es fix: resources search button and grid update on property change for form builder feat: add missing unsubscriptions for all the logic related to the question types in the survey forms feat: update some question interfaces with new properties regarding the aforementioned reason
@unai-reliefapp unai-reliefapp marked this pull request as ready for review March 6, 2024 09:28
@unai-reliefapp
Copy link
Contributor Author

@AntoineRelief Changes made set in the description and in the related ticket
I think there is plenty to merge, next step I'll go to is to make an error handler service in order to avoid multiple error handlers everywhere, or missing ones, and keep a consistent error messaging logic across the app

KR, Unai

@AntoineRelief
Copy link
Collaborator

@unai-reliefapp
Nice
Perhaps we should create separate branches ( even if they use the other ones ) so the PR is not becoming bigger

@unai-reliefapp
Copy link
Contributor Author

@unai-reliefapp Nice Perhaps we should create separate branches ( even if they use the other ones ) so the PR is not becoming bigger

Yes, i'll create another branch for the error handler using same ticket number if it's okay

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in code review Under review keep Do not delete refactor Refactor of the code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants