search

quantified-uncertainty / metaforecast

Fetch forecasts from prediction markets/forecasting platforms to make them searchable. Integrate these forecasts into other services.
https://metaforecast.org/
MIT License
56 stars 5 forks source link

feat: add contrib folder #85

Closed NunoSempere closed 2 years ago

NunoSempere commented 2 years ago

Thoughts on location, or on whether this is a good idea at all?

vercel[bot] commented 2 years ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
metaforecast ✅ Ready (Inspect) Visit Preview May 19, 2022 at 7:59PM (UTC)
berekuk commented 2 years ago

Is this for scripts using public APIs (i.e. GraphQL) only, or do you expect that some scripts are going to query the Postgres database or internal APIs, like stuff from src/backend/utils/misc/ does?

In the latter case I'd prefer for it to be located inside src/ and be written with TypeScript (even if with lots of any if authors are not experienced), for easier refactoring when internal APIs change.

In the former case, I don't care :)

Naming depends on what you have in mind here, do you assume that people (even if just you) will use this as a main way to store their code, or is this more like an example? I'd expect most people who are not you will want to store their code in their own repos.

PS: For providing examples there's a common practice to have an examples folder, e.g. https://github.com/vercel/next.js/tree/canary/examples.

NunoSempere commented 2 years ago

Is this for scripts using public APIs (i.e. GraphQL) only, or do you expect that some scripts are going to query the Postgres database or internal APIs, like stuff from src/backend/utils/misc/ does?

This would be for scripts using our public APIs.

Naming depends on what you have in mind here, do you assume that people (even if just you) will use this as a main way to store their code, or is this more like an example? I'd expect most people who are not you will want to store their code in their own repos.

I'm assuming that people might want to do neat things with the Metaforecast api, and might want to share them back with other people, as in here.