Andras/BoundlessFlowCampus2K
4
7
Fork 0
Code Issues 90 Pull requests 7 Projects Releases Packages Wiki Activity Actions

Research/implement structure of components in project #231

New issue
Closed
opened 2026-04-10 11:27:32 +00:00 by b24johka · 3 comments
b24johka commented 2026-04-10 11:27:32 +00:00
Collaborator
Copy link
No description provided.
b24jonel referenced this issue from a commit 2026-04-10 14:16:45 +00:00
#231 Restructruring
hGustavs commented 2026-04-13 13:40:28 +00:00
Owner
Copy link

We want a simple structure, with plenty reuse.

Can we make an architecture diagram in this issue as a basis for the discussion?

We want a simple structure, with plenty reuse. Can we make an architecture diagram in this issue as a basis for the discussion?
b24jonel commented 2026-04-16 09:27:46 +00:00
Collaborator
Copy link

The title may be misleading what this issue was about was moving the components in the front end from App.js to their own components which are called via routing. The components are now accessible via for example the clickable links in the navbar and footer. Cards are now only shown on the home page instead of every page like it was before. If anything I think a class diagram would be better in this situation since it's about how the classes interact. Does this clarify the issue or should I make a architecture/class diagram still?

The title may be misleading what this issue was about was moving the components in the front end from App.js to their own components which are called via routing. The components are now accessible via for example the clickable links in the navbar and footer. Cards are now only shown on the home page instead of every page like it was before. If anything I think a class diagram would be better in this situation since it's about how the classes interact. Does this clarify the issue or should I make a architecture/class diagram still?
a24sakma commented 2026-05-07 19:21:56 +00:00
Collaborator
Copy link

we use reusable components. I close this issue as it is implemented.

we use reusable components. I close this issue as it is implemented.
b25marem referenced this issue from a commit 2026-05-15 08:56:00 +00:00
#231 Restructruring
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
#1236-edit-mode-txt
#1229-generic-themed-buttons
Add-an-option-to-set-no-image-to-image-view-1227
#1242-prog-bar-colors-fix
#1239-Remove-Vertical-Scroll
Image-view-error-1230
Make-the-card-title-and-header-of-card-uniform-1233
both_teams_week_8
team_2_week_7
team_1_week_7
temp_branch_week_7
team_2_week_6
team_1_week_6
team_2_week_5
team_1_week_5
temp_branch_week_5
team_2_week_4
team_1_week_4
week_4_temp_branch
temp-branch-week-3
team_2_week_3
team_1_week_3
team_2_week_2
team_1_week_2
temp-week-2-merge-branch
team_2_week_1
team_1_week_1
No results found.
Labels
Clear labels   
_CRITICAL_

Only use this label for critical tasks that are project-scope,and must be addressed ASAP.

  
API

   
app

   
backEnd

   
Blocked, waiting for further changes

   
bug

Something is not working

  
cleanup

Issues to cleanup the codebase (restructure folders, remove deprecated or smelly code)

  
close

Issue to close

  
design

   
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
feature request

   
frontEnd

   
help wanted

Need some help

  
invalid

Something is wrong

  
low priority

   
needs input

Issue needs input from product owner or customer

  
needs review

issue is in need of review

  
project documentation

   
question

More information is needed

  
research

   
reviewed

This Issue has been reviewed

  
script

   
security

use this for security-related issues

  
SQL

  
style

   
testing

   
topLevel

Reserved for top-level, project-wide issues.

  
wontfix

This won't be fixed

No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
b24jonel
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Andras/BoundlessFlowCampus2K#231
No description provided.