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

249: Basic navigation and project folder structure #256

Open
wants to merge 21 commits into
base: main
Choose a base branch
from

Conversation

volkramweber
Copy link
Collaborator

Short description

Adds bottom navigation bar, main routes and screens.

Proposed changes

  • Adds router with main routes
  • Adds bottom navigation bar including links to the main routes

Side effects

None.

Testing

Navigate to the main routes of the app.

Resolved issues

Fixes: #249


@volkramweber volkramweber linked an issue Oct 27, 2024 that may be closed by this pull request
3 tasks
@volkramweber
Copy link
Collaborator Author

I merged branches of not already merged pull requests to this branch. Not sure, if this was the right way? Please let me know.

@steffenkleinle
Copy link
Contributor

steffenkleinle commented Oct 28, 2024

I merged branches of not already merged pull requests to this branch. Not sure, if this was the right way? Please let me know.

Hmm, I personally think that this should be avoided. This way, reviewing your PR is quite hard as it is not clear at all which changes stem from your PR and which from other PRs until all other PRs are merged to your base branch (i.e. main). Usually, branches and PRs should only include the commits of max. one other branch than main imo, so you can just base the PR on that branch instead of main (see e.g. #255). Otherwise, its probably better to focus on merging the other PRs fast.
Specifically in this case, is your PR really dependent/based on any of the other PRs?

@volkramweber
Copy link
Collaborator Author

I merged branches of not already merged pull requests to this branch. Not sure, if this was the right way? Please let me know.

Hmm, I personally think that this should be avoided. This way, reviewing your PR is quite hard as it is not clear at all which changes stem from your PR and which from other PRs until all other PRs are merged to your base branch (i.e. main). Usually, branches and PRs should only include the commits of max. one other branch than main imo, so you can just base the PR on that branch instead of main (see e.g. #255). Otherwise, its probably better to focus on merging the other PRs fast. Specifically in this case, is your PR really dependent/based on any of the other PRs?

Yes, in this case the other PRs should be merged fast.
This PR is dependent on the other PRs/Issues:

But I agree with you, it's hard to review and not clear.
Let's merge the other PRs fast.
I hope these kind of dependencies between PRs do not happen in the future.

@steffenkleinle steffenkleinle changed the title 249 basic navigation and project folder structure 249: Basic navigation and project folder structure Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Basic Navigation and Project Folder Structure
2 participants