←back to thread

415 points joice | 5 comments | | HN request time: 1.114s | source
Show context
simonhamp ◴[] No.41860714[source]
I am trying to submit my funding.json, it validates when I check the validator, but fails when I submit with the error: "too many lines in the .well-known list"

I have 1 line in my .well-known lists

Here's my funding.json:

https://nativephp.com/funding.json

Can someone help me figure out what I'm doing wrong?

replies(2): >>41860915 #>>41861115 #
1. pacmansyyu ◴[] No.41861115[source]
Hi, I'm from the team at Zerodha. It seems as if the well-known URL for the laravel repository points to the GitHub page[1] instead of the URL for the raw code[2]. Changing the well-known URL to the raw code path should fix this issue. Will pass this feedback on to the team to improve the experience, thanks!

[1]: https://github.com/nativephp/laravel/blob/main/.well-known/f... [2]: https://raw.githubusercontent.com/nativephp/laravel/refs/hea...

replies(1): >>41861237 #
2. simonhamp ◴[] No.41861237[source]
Sure, but that's not how it's demonstrated in the docs...

I've updated it, but that also doesn't work AND fails validation because:

"projects[0].repositoryUrl.url and `projects[0].repositoryUrl.wellKnown` hostnames do not match"

replies(1): >>41861341 #
3. pacmansyyu ◴[] No.41861341[source]
Apologies for my previous misguiding comment. We have figured out the issue and a fix is being implemented right now to handle URLs for GitHub repositories and suffix them with `?raw=true` to automatically to fetch the raw file. The fix should be live soon.

In the meanwhile, if you would like to submit the project, you could use the following URL which redirects to the `raw.githubusercontent.com` page: https://github.com/nativephp/laravel/raw/main/.well-known/fu...

I hope this helps!

replies(1): >>41861464 #
4. simonhamp ◴[] No.41861464{3}[source]
Awesome! It worked! Thanks so much.

Looking forward to being listed and considered for funding :)

replies(1): >>41862105 #
5. pacmansyyu ◴[] No.41862105{4}[source]
Cheers! The issue has been fixed now and is live. Thanks a lot for your feedback :)