-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[#58345] Primerize Relations tab #16989
Merged
HDinger
merged 52 commits into
dev
from
implementation/58345-re-design-relations-tab-according-to-figma-mockups
Nov 26, 2024
Merged
[#58345] Primerize Relations tab #16989
HDinger
merged 52 commits into
dev
from
implementation/58345-re-design-relations-tab-according-to-figma-mockups
Nov 26, 2024
Conversation
This file contains 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
aaron-contreras
force-pushed
the
implementation/58345-re-design-relations-tab-according-to-figma-mockups
branch
2 times, most recently
from
October 18, 2024 22:26
ca640c9
to
fa664f8
Compare
aaron-contreras
force-pushed
the
implementation/58345-re-design-relations-tab-according-to-figma-mockups
branch
5 times, most recently
from
October 28, 2024 13:16
a0efe87
to
05ad841
Compare
aaron-contreras
force-pushed
the
implementation/58345-re-design-relations-tab-according-to-figma-mockups
branch
from
October 29, 2024 16:02
05ad841
to
97bd373
Compare
aaron-contreras
force-pushed
the
implementation/58345-re-design-relations-tab-according-to-figma-mockups
branch
14 times, most recently
from
November 6, 2024 12:27
9ae2cbe
to
6f16dd8
Compare
aaron-contreras
force-pushed
the
implementation/58345-re-design-relations-tab-according-to-figma-mockups
branch
3 times, most recently
from
November 8, 2024 12:59
344a7e0
to
4a23389
Compare
A relation should be read as `<from> <relation_type> <to>`: for instance `Relation.create(from_id: 123, to_id: 456, relation_type: :follows)` means that work package 123 follows work package 456, which means that work package 123 is the successor of work package 456, or that work package 456 is the predecessor of work package 123. The translations were inverted. Also used `shared_let` in specs to speed them up a little.
…ersion. The only remaining part is about updating the frame, when the workPackage is updated elsewhere (e.g by adding a child to an embedded table)
3 tasks
…cause of a cache invalidation. Thus we avoid an unneccessary frame reload which also caused tests to flicker
…o the height of its content
…dy height is fixed to the height of its content
…e data. Further, when manually updating the objects do not execute the observable again
…d use system attributes
…cument it (#17234) * create a component for WP info line * fix spacing * change component name and simplify code * add a preview for lookbook * pass workpackage itself to the component, not its id * render info line component inside the relation component * First draft of Lookbook docs * add some docs for info line component * make fon-size configurable * make id clickable * use info-line component in meeting agenda item * use info-line component in hover card --------- Co-authored-by: Parimal Satyal <[email protected]>
…en if the subject spans muliple lines
HDinger
force-pushed
the
implementation/58345-re-design-relations-tab-according-to-figma-mockups
branch
from
November 25, 2024 12:08
598582f
to
19eb34a
Compare
…r workPackage and Relation updates have fired way too often
…according-to-figma-mockups
oliverguenther
approved these changes
Nov 25, 2024
HDinger
deleted the
implementation/58345-re-design-relations-tab-according-to-figma-mockups
branch
November 26, 2024 07:38
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ticket
https://community.openproject.org/work_packages/58345
Includes https://community.openproject.org/projects/openproject/work_packages/58734/activity as well
What are you trying to accomplish?
Primerize the Relations tab according to Figma mockups
Note: This is an implementation chunk of https://community.openproject.org/projects/stream-planning-and-reporting/work_packages/22360
What approach did you choose and why?
Followed the patterns established when primerizing the Activity tab and the Meetings tab
Missing specs to fix
rspec ./modules/boards/spec/features/board_navigation_spec.rb:158 # Work Package boards spec navigates to the details view and reloads (see #49678)
rspec ./modules/boards/spec/features/board_navigation_spec.rb:127 # Work Package boards spec navigates from boards to the WP details view then go to full view then go back (see #33747)
Merge checklist