extensions
extensions copied to clipboard
Add `fantasy-premier-league-rankings` extension
Description
This is an extension which allows a user to input their fantasy premier league team id and keep track of their rankings across all the leagues they are entered in.
Screencast
https://user-images.githubusercontent.com/47414652/189547553-1dc0f772-aa34-4dbf-896e-c06f57172108.mp4
Checklist
- [X] I read the extension guidelines
- [X] I read the documentation about publishing
- [X] I ran
npm run buildand tested this distribution build in Raycast - [X] I checked that files in the
assetsfolder are used by the extension itself - [X] I checked that assets used by the
READMEare placed outside of themetadatafolder
Congratulation on your new Raycast extension! :rocket:
We will review it shortly. Once the PR is approved and merged, the extension will be available on the Store.
I'm going to fix the screenshots shortly and shoot them on a retina screen instead to make sure they are the right resolution
Hi @hwb15 👋
Thanks for your contribution, could you look into the linting issues?
When I test this extension I just get this result, do you happen to know what might cause this?

12:54:43.422 [AxiosError: Request failed with status code 403] {
code: 'ERR_BAD_REQUEST',
config: {
transitional: {
silentJSONParsing: true,
forcedJSONParsing: true,
clarifyTimeoutError: false
},
adapter: [Function: httpAdapter],
transformRequest: [ [Function: transformRequest] ],
transformResponse: [ [Function: transformResponse] ],
timeout: 0,
xsrfCookieName: 'XSRF-TOKEN',
xsrfHeaderName: 'X-XSRF-TOKEN',
maxContentLength: -1,
maxBodyLength: -1,
env: { FormData: [Function] },
validateStatus: [Function: validateStatus],
headers: {
Accept: 'application/json, text/plain, */*',
authority: 'users.premierleague.com',
'cache-control': 'max-age=0',
'upgrade-insecure-requests': '1',
origin: 'https://fantasy.premierleague.com/',
'user-agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.0.0 Safari/537.36',
'sec-fetch-site': 'same-site',
'sec-fetch-mode'<…>
Hi @hwb15 👋
Thanks for your contribution, could you look into the linting issues?
When I test this extension I just get this result, do you happen to know what might cause this?
12:54:43.422 [AxiosError: Request failed with status code 403] { code: 'ERR_BAD_REQUEST', config: { transitional: { silentJSONParsing: true, forcedJSONParsing: true, clarifyTimeoutError: false }, adapter: [Function: httpAdapter], transformRequest: [ [Function: transformRequest] ], transformResponse: [ [Function: transformResponse] ], timeout: 0, xsrfCookieName: 'XSRF-TOKEN', xsrfHeaderName: 'X-XSRF-TOKEN', maxContentLength: -1, maxBodyLength: -1, env: { FormData: [Function] }, validateStatus: [Function: validateStatus], headers: { Accept: 'application/json, text/plain, */*', authority: 'users.premierleague.com', 'cache-control': 'max-age=0', 'upgrade-insecure-requests': '1', origin: 'https://fantasy.premierleague.com/', 'user-agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.0.0 Safari/537.36', 'sec-fetch-site': 'same-site', 'sec-fetch-mode'<…>
👋 @pernielsentikaer
Let me take a look at this, seems to be an error with the API the extension uses to fetch the fantasy premier league data.
All the linting errors are sorted, the test error that currently shows seems to be when the extension was going to be built and added to the store but another extension visual-studio-code-recent-projects that was being updated at the same time had a build failure for No loader is configured for ".wasm" files which is why it looks like the build failed on this extension.
I'll get back to you shortly!
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊
I'm closing this due to inactivity; feel free to comment in the thread when you're ready to continue working on it 🙂 You can also catch us in Slack if you want to discuss.
Hi @hwb15 👋 Thanks for your contribution, could you look into the linting issues? When I test this extension I just get this result, do you happen to know what might cause this?
12:54:43.422 [AxiosError: Request failed with status code 403] { code: 'ERR_BAD_REQUEST', config: { transitional: { silentJSONParsing: true, forcedJSONParsing: true, clarifyTimeoutError: false }, adapter: [Function: httpAdapter], transformRequest: [ [Function: transformRequest] ], transformResponse: [ [Function: transformResponse] ], timeout: 0, xsrfCookieName: 'XSRF-TOKEN', xsrfHeaderName: 'X-XSRF-TOKEN', maxContentLength: -1, maxBodyLength: -1, env: { FormData: [Function] }, validateStatus: [Function: validateStatus], headers: { Accept: 'application/json, text/plain, */*', authority: 'users.premierleague.com', 'cache-control': 'max-age=0', 'upgrade-insecure-requests': '1', origin: 'https://fantasy.premierleague.com/', 'user-agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.0.0 Safari/537.36', 'sec-fetch-site': 'same-site', 'sec-fetch-mode'<…>👋 @pernielsentikaer
Let me take a look at this, seems to be an error with the API the extension uses to fetch the fantasy premier league data.
All the linting errors are sorted, the test error that currently shows seems to be when the extension was going to be built and added to the store but another extension
visual-studio-code-recent-projectsthat was being updated at the same time had a build failure forNo loader is configured for ".wasm" fileswhich is why it looks like the build failed on this extension.I'll get back to you shortly!
Hi @pernielsentikaer !
I'm happy to open a new PR now, and feel the extension is ready again for store - I have worked on sorting the issues with 403 responses to requests and have fixed it up both through the extension and also a few changes on the backend.
RE: linting errors, explanation above from the build failure message is in regards to another extension so this shouldn't cause any issues w/ my own extension.
Thank you 🙏