apibr / vagas-aggregator-ui Goto Github PK

Is your feature request related to a problem? Please describe.
So this feature is related to a problem, there is no proper error-handling and this is necessary for an deployed application because, if by any chance any error occurs the whole application will crash, preventing the app from becoming unresponsive or crashing we need error-handling.

Describe the solution you'd like
Centralized Error Handling: Global error boundaries allow you to centralize error handling logic in one place (e.g., at the app's entry point), making it easier to manage and maintain error-handling code.

Consistency: With a global error boundary, you can ensure a consistent error-handling strategy throughout your application. You don't have to repeat error-handling code in multiple places.

Describe alternatives you've considered
A descent alternative could be to use simple try and catch blocks, but that won't be providing us robustness that is required to be maintained in a deployed application.

Additional context
Please feel free to ask any questions and I would be happy to add this feature to enhance the robustness of the application, kindly assign me this issue.

Is your feature request related to a problem? Please describe.
I would like to have a link in menu to request a new feature or report a existing bug.

Describe the solution you'd like
Add a link in menu to redirect to issue creation page on GitHub for this repository, since it's public and everyone can create an issue.

Is your feature request related to a problem? Please describe.
In the Repositories pages add an option to hide repositories with zero issues (vacancies).

Describe the solution you'd like
A switch button (on/off or enable/disable style) to hide/show repositories with no vacancies.

Technical notes:

• By default should hide (disabled/off).
• The selected value should be stored in localStorage for a stateful experience.
• The behaviour should be also enabled by the query string parameter.
• Use the React Switch component

Remarks

As the first step, we can do it only on the front-end side (UI, this repository), but later we can implement it on the back-end (API) side as well and filter by query-string too.

The API already includes the ability to filter empty (no vacancies) repositories.
Just need to add a query string value hide-empty=true to the URL and it will remove repositories/organizations with no issues/vacancies.

Hide: https://apibr.com/vagas/api/v1/repositories?per_page=10&page=1&hide-empty=true
Show: https://apibr.com/vagas/api/v1/repositories?per_page=10&page=1&hide-empty=false

CodeFactor found multiple issues:

Duplicate Code

• src\Components\Repositories\RepositoriesList.js:33-42
• src\Components\Issues\IssuesList.js:101-110
• src\Components\Repositories\RepositoriesSelect.js:40-51
• src\Components\Labels\LabelsSelect.js:38-49
• src\Components\Authors\AuthorsSelect.js:41-52

Is your feature request related to a problem? Please describe.
Add a badge to issues with stale label informing that issue will be closed soon

Describe the solution you'd like
Add a badge side of issue title with red board [STALE]

Is your feature request related to a problem? Please describe.
Show comments count in the issue

Describe the solution you'd like
Use the API node comments to display how many comments the issue received.

Describe the bug
The timestamp component within the card is overflowing and extending beyond the card boundaries. This is causing a visual misalignment and disruption in the layout of the card. The timestamp should remain within the designated card area to maintain a consistent and aesthetically pleasing design.

To Reproduce
Steps to reproduce the behavior:

1. Go to here
2. Scroll to see the bug in the cards.

Expected behavior
The timestamp component within the card should be appropriately styled and positioned to fit comfortably within the confines of the card. It should align with the card's layout and not extend beyond its edges. This ensures a visually pleasing presentation and maintains the overall coherence of the card's design.

Screenshots

Desktop (please complete the following information):

• OS: [e.g. Windows]
• Browser [chrome, edge]
• Current Version

Additional context
Currently working on this issue. Kindly, assign me this issue.
Please feel free to use comment section to start any discussion or ask any questions.

Adjust alignment in button Ver vaga no GitHub

Current:

Expected:

Is your feature request related to a problem? Please describe.
Add i18n support

Is your feature request related to a problem? Please describe.
Add formatting to the issue title in the part with parentheses.

Describe the solution you'd like
Use regular expression to replace (anything) in the issue title with label formatting.

Description

Currently receiving error messages in Google Search Console related to Duplicate without user-selected canonical
This issue is caused by the fact that React dynamically handles the URL in the front end, but they are also present in the sitemap.xml generated by the service.

Screenshots

Additional information

The proposal solution is to rename the index.html to index.php and add include a file named metatags.php that will generate the metatags based on current URI.

Describe the bug
The current UI layout presents an issue where a logo and a hyperlink are overlapping with the date and timestamp as you can see in the image below within the card component. This overlap is negatively affecting the visual and functional aspects of the user interface.

To Reproduce
Steps to reproduce the behavior:

1. Navigate to here
2. Observe the logo and the hyperlink within the card, i think its a github logo (not sure though what its called!!) with "blankapf" as text which shall be linked to some other resource possibly.
3. Note that the logo and hyperlink are overlapping with date and timestamp, causing a visual inconsistency and potential clickability issues.

Expected behavior
The logo and hyperlink should be appropriately spaced and not overlap, ensuring a clean and user-friendly design. Users should be able to interact with the hyperlink without any visual hindrance or any kind of hindrance.

• Browser [chrome]
• Version [current version that is deployed]

Additional context
I would be glad if this bug is assigned to me.

Please feel free to use comment section for any further discussion.

Is your feature request related to a problem? Please describe.
Add Sonar Cloud badges

Is your feature request related to a problem? Please describe.
Add formatting to the issue title in the part with square brackets.

Describe the solution you'd like
Use regular expression to replace [anything] in the issue title with label formatting.

Is your feature request related to a problem? Please describe.
Add a badge (in the menu) with the API version and date information.

Describe the solution you'd like

• The API returns two headers (X-api-version and X-api-date).
• Use this information to display a badge on the menu of the application.
• Maybe it requires a dedicated call to API to grab this information and store it.
• The badges should link to the Swagger address.

Describe alternatives you've considered
Use some API call already in place to grab this information or do a dedicated call only to grab this information (a head request)?

Add badges from Code Climate