ash-jc-allen / find-a-pr Goto Github PK

There are some archived repos in config/repos.php, I think it would be good if they are ignored when crawling. They also should be hidden in the sidebar.

public/logs/laravel.log
laravel.EMERGENCY: Unable to create configured logger. Using emergency logger

Solution:
remove in .env
LOG_DEPRECATIONS_CHANNEL=null

Should this be updated in .env.example ?

It seems that the sorting from the sorting order isn't pulled anymore from the URL. I think this might be something I've broken at some stage (but not sure how).

I might put some tests (maybe Dusk tests) together because to stop something like this from breaking again in the future.

Example: https://findapr.io/?sortField=repoName going to that repo should sort by the repoName field but instead it sorts by random

Interesting project!
I had the same idea but not for specific technology. I wanted to make it based on type of issues. I think both can be combined!

Anyway, I wanted to ask about license of this project. There is no license in the repo. The license section in the README also talks about Laravel license. May you please make it clear that if this project is a Free/Libre and Open Source software?

Thanks

To get an MVP together quickly, I didn't set up Laravel Mix properly.

So, the image fields are directly in the resources folder. It would be nicer to have these in the resources and they could be copied over during the deployment/build process.

The app is also currently using Tailwind via the CDN. It would be nice to be using Tailwind via NPM instead so that we can purge the CSS during the build process.

We need to add instructions to the site to explain to repo maintainers how they can open up their projects for contribution.

They just need to add at least one of the labels that we've set in the config/repos.php file to their issues to be picked up,

Using Firefox.

It would be nice to have Larastan in the project and a Larastan workflow running on GitHub Actions for each PR.

There's a little problem in mobile view.

This is mainly a hypothetical idea for a feature, but it'd be pretty cool if we could add push notifications to the Find A PR PWA. I don't know if this is feasible (or even worth it), but I think it could be a cool way of getting an update straight to your phone whenever a new issue is available

It would be better to have all Tailwind class names sorted in same and correct way, a linter would solve this problem.
InteliSense which was mentioned by core team in documentation would handle this.
It also helps for code readability and make contribution more easier.

🚀 This is an example first issue. This serves no purpose other than checking that the issue is being rendered properly in findapr.io.

I think it'd be nice to be able to press the / key on the keyboard to be able to autofocus on the search bar.

When I install findapr, I got 503 error. I think that comes from bugsnag, so I established bugsnag API key. here I found the solution and it still does not work.

[2022-08-12 15:24:23] laravel.EMERGENCY: Unable to create configured logger. Using emergency logger. {"exception":"[object] (InvalidArgumentException(code: 0): Log [deprecations] is not defined. at /home/shaungbhone/Desktop/find-a-pr/vendor/laravel/framework/src/Illuminate/Log/LogManager.php:207) [stacktrace] #0 /home/shaungbhone/Desktop/find-a-pr/vendor/laravel/framework/src/Illuminate/Log/LogManager.php(132): Illuminate\\Log\\LogManager->resolve() #1 /home/shaungbhone/Desktop/find-a-pr/vendor/laravel/framework/src/Illuminate/Log/LogManager.php(119): Illuminate\\Log\\LogManager->get() #2 /home/shaungbhone/Desktop/find-a-pr/vendor/laravel/framework/src/Illuminate/Log/LogManager.php(108): Illuminate\\Log\\LogManager->driver()

Environment ....................................................................................................................
Application Name ....................................................................................................... Laravel
Laravel Version ......................................................................................................... 9.24.0
PHP Version .............................................................................................................. 8.1.0
Composer Version ........................................................................................................ 2.1.14
Environment .............................................................................................................. local
Debug Mode ............................................................................................................. ENABLED
URL .................................................................................................................. localhost
Maintenance Mode ........................................................................................................... OFF

Cache ..........................................................................................................................
Config .............................................................................................................. NOT CACHED
Events .............................................................................................................. NOT CACHED
Routes .............................................................................................................. NOT CACHED
Views ................................................................................................................... CACHED

Drivers ........................................................................................................................
Broadcasting ............................................................................................................... log
Cache ..................................................................................................................... file
Database ................................................................................................................. mysql
Logs ................................................................................................... stack / single, bugsnag
Mail ...................................................................................................................... smtp
Queue ..................................................................................................................... sync
Session ................................................................................................................... file

At the moment, there isn't a list of the GitHub repos that are being crawled for the list. It'd be nice to have a list of the repos on the page on the left or right side of the page.

As an enhancement, the repos could maybe be used click on to filter the list to only show issues from the given repo.

vite public/hot file:
http://0.0.0.0:5173

See: laravel/vite-plugin#28

At the moment, the repos are hardcoded in the config/repos.php file. It would be nice if there was a way for us to automatically add more repos to grow the list? Maybe using the GitHub API to crawl through any PHP/Laravel related repos (I don't know if this is possible).

I'm open to suggestions on this to make it easier for the list to maintain itself :)

I think it'd be nice to have the functionality to "ignore" a particular issue. So, if you aren't interested in attempting to take on an issue, you could press an "ignore" button that would use the browser's local storage to hide the issue. Then on every subsequent page load, any ignored issues won't be displayed.

I think using Alpine would be the ideal way of implementing this.

At the moment, the README is still using the default Laravel content.

This needs updating with content that is specific to this project.

Ignore this issue. It is here as a test issue for findapr.io code

codeblock

The GitHub API provides information in the issues response with a list of the reactions (e.g. 👍 , 👎 ). It would be pretty nice to have these displayed in the cards on the site.

At the moment, the site isnt responsive and can't be viewed properly on mobile. It would be nice to have a mobile/tablet version.

I think it'd be nice to have a search bar for filtering the issues based on the:

• Repo name
• Issue name
• Creator's name

I think for the time being, a client-side search would be fine for this. But, I'd also be happy with a server-side search (whatever would be the easiest to implement).

It can be a better user experience to open links in new tabs when clicked such as issue title, repository, view button, and issue creator.

To increase the reach of issues that need help, we could tweet them automatically.

Now that the site has support for being used on a mobile, I think it'd be really cool to take it a step further and add PWA functionality.

This could allow users to add the site as a PWA to their phones and PCs so that they can quickly jump in and check for open issues.

Of course, this isn't going to serve a huge amount of purpose, but could be a pretty good chance to experiment with some cool features.

Everyone loves dark mode! I think it'd be a nice addition to have a dark mode toggle for users to switch between light/dark/system.

At the moment, the PRs are displayed in the order that they're returned from the GitHub API.

It would be nice to be able to sort them based on a few different fields:

• Repo
• Date
• Alphabetical