-
Notifications
You must be signed in to change notification settings - Fork 314
Development
: Use signals in title channel name component
#10979
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
florian-glombik
wants to merge
67
commits into
develop
Choose a base branch
from
chore/development/use-signals-in-title-channel-name-component
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Development
: Use signals in title channel name component
#10979
florian-glombik
wants to merge
67
commits into
develop
from
chore/development/use-signals-in-title-channel-name-component
+347
−293
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
End-to-End (E2E) Test Results Summary
|
End-to-End (E2E) Test Results Summary
|
…annel-name-component
End-to-End (E2E) Test Results Summary
|
ahmetsenturk
previously approved these changes
Jun 13, 2025
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.
code lgtm 👍
…annel-name-component # Conflicts: # jest.config.js
5766c11
End-to-End (E2E) Test Results Summary
|
End-to-End (E2E) Test Results Summary
|
chuuuun
previously approved these changes
Jun 14, 2025
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.
Tested on TS4, user 17. status bars updates properly in mentioned domains.
44ab605
End-to-End (E2E) Test Results Summary
|
…annel-name-component
End-to-End (E2E) Test Results Summary
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
client
Pull requests that update TypeScript code. (Added Automatically!)
exercise
Pull requests that affect the corresponding module
fileupload
Pull requests that affect the corresponding module
iris
Pull requests that affect the corresponding module
lecture
Pull requests that affect the corresponding module
modeling
Pull requests that affect the corresponding module
programming
Pull requests that affect the corresponding module
ready for review
text
Pull requests that affect the corresponding module
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
General
Client
Motivation and Context
We want to exploit the language features that Angular offers. In most cases, signals offer a more intuitive and more performant solution than raw RxJS subscriptions.
In the long run, we can simplify the status bar updates and rely on computed signals instead of registering effects and defining update methods, which is a much cleaner and easier to maintain approach. Exploiting signals also yields better performance and less UI updates.
This PR is a step in that direction.
Description
formValid
andformValidChanges
fromtitle-channel-name.component.ts
title-channel-name.component.ts
is usedtitle-channel-name.component.ts
Development
: Improve client test coverage #11016Steps for Testing
Test this as instructor
TextExercises
ModelingExercises
ProgrammingExercises
FileUploadExercises
Lectures
The behaviour should not have changed in comparison to develop when editing the title of one of the listed entities.
Testserver States
You can manage test servers using Helios. Check environment statuses in the environment list. To deploy to a test server, go to the CI/CD page, find your PR or branch, and trigger the deployment.
Review Progress
Code Review
Manual Tests
Test Coverage
Client
Screenshots
Apperance should not have changed, see this example:
Summary by CodeRabbit
New Features
Refactor
Bug Fixes
Style
Tests
Chores