TeamAmaze / TeamAmaze/AmazeFileManager

Fixed Navigation path

Open
#2,764 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Navigation Issue-Bug
Dominant language
Kotlin
Stars
6.4k
Forks
1.7k
Avg merge
3d 9h
Merged PRs (30d)
1

Description

Is your feature request related to a problem? Please describe.
In amaze if you go back to a directory then you cant go forward from the upper navigation because the navigation path changes when going backwards.

https://user-images.githubusercontent.com/48226312/131681854-f749dd93-81e6-4879-8140-6c0542932ae0.mp4

For ex in the video once you go to "DATA" you cant go back to "APP" directory.

Screenshot_2021-09-01-19-22-17
Screenshot_2021-09-01-19-16-51
So amaze supports only backward navigation.

But in MaterialFiles it remain fixed
Screenshot_2021-09-01-19-20-51
I can go both both backward/forward in MaterialFiles.

Describe the solution you'd like
The navigation path should remain fixed even when you comback from a directory.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the navigation shown in the issue's video: move from APP to DATA, go back, and try to return to APP using the upper navigation path. Done means the navigation path remains fixed when returning from a directory and supports both backward and forward navigation.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.