You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
We have tag pages that work similarly to search pages. (ex: Frontend)
Search and tag pages work with the same logic, using the 'job-listing-with-filters' component. The widget area (for filtering) and job-listing works in 'job-listing-with-filters' component.
When you are on any label page, when you need to filter, you go out of the label page.
For example; If you enter the 'Frontend' tag page, mark Istanbul as the City in the filtering area and press the 'Ara(Search)' button, you will go to the search page for Istanbul. The same problem applies to all tag fields (keyword, city, and type of operation). Actually, it was supposed to filter inside the tag.
This bug is primarily a 'business' bug. First, we need to analyze this on the 'business' side.
We have tag pages that work similarly to search pages. (ex: Frontend)
Search and tag pages work with the same logic, using the 'job-listing-with-filters' component. The widget area (for filtering) and job-listing works in 'job-listing-with-filters' component.
When you are on any label page, when you need to filter, you go out of the label page.
For example; If you enter the 'Frontend' tag page, mark Istanbul as the City in the filtering area and press the 'Ara(Search)' button, you will go to the search page for Istanbul. The same problem applies to all tag fields (keyword, city, and type of operation). Actually, it was supposed to filter inside the tag.
This bug is primarily a 'business' bug. First, we need to analyze this on the 'business' side.
Ideas are welcome.
Screenshot
The text was updated successfully, but these errors were encountered: