Migrate

[fawazahmed0]

• migrate all issues
• create new repo for npm currency-api (update current readme to point to it)
• check compressed tarball feasibility (7zip gzip) (415 too many files issue, also tried npm-registry-client )
• support only one end point
• make task list
• migrate to npm & pages
• create readme
• warn users with steps to migrate ( in json & readme )
• push curr-api files with commit history here (check first)
• other cdn (caching issue, max 1 day) and Other options for cdn #42 (possibly esm.sh )

[Advaith3600]

There is no /currencies/{currencyCode}/{currencyCode} endpoint in this new API, so please only use /currencies/{currencyCode}

Is this endpoint going to be added in the future?

[fawazahmed0]

It will not be added in future, because npm doesn't support too many files, it gives 415 too many files Error

[omnigenous]

@fawazahmed0 Could you please keep YYYY-MM-DD format?

[yangshun]

@fawazahmed0 Thanks for the quick actions in getting the API back up!

Just wanted to report that the new version API (e.g. https://cdn.jsdelivr.net/npm/@fawazahmed0/[email protected]/v1/currencies/usd.json) doesn't seem to work. It'd also be good to continue supporting the old date format YYYY-MM-DD, not sure why it has to be changed.

[fawazahmed0]

@yangshun Dates are available from 2024-03-02
This should work:
https://cdn.jsdelivr.net/npm/@fawazahmed0/[email protected]/v1/currencies/usd.json

@omnigenous , no its not possible, the dates has to follow semver pattern. You can use regex to convert , eg:

"2024-03-02".replaceAll('-','.').replace(/\.0+(\d+)/gi , ".$1")

[omnigenous]

I was using the API in my bash script :D

I guess I could do date -u +%Y.%-m.%-d

[fawazahmed0]

I have added YYYY-MM-DD support. please refer the readme