Skip to content

Commit 2b4340a

Browse files
authored
V0.0.19.0 forex (#28)
* update version * forex list, full forex quote list * forex complete with tests
1 parent 8de6e66 commit 2b4340a

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

61 files changed

+15004
-14173
lines changed

.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 38 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -1,38 +1,38 @@
1-
---
2-
name: Bug report
3-
about: Create a report to help us improve
4-
title: ''
5-
labels: ''
6-
assignees: ''
7-
8-
---
9-
10-
**Describe the bug**
11-
A clear and concise description of what the bug is.
12-
13-
**To Reproduce**
14-
Steps to reproduce the behavior:
15-
1. Go to '...'
16-
2. Click on '....'
17-
3. Scroll down to '....'
18-
4. See error
19-
20-
**Expected behavior**
21-
A clear and concise description of what you expected to happen.
22-
23-
**Screenshots**
24-
If applicable, add screenshots to help explain your problem.
25-
26-
**Desktop (please complete the following information):**
27-
- OS: [e.g. iOS]
28-
- Browser [e.g. chrome, safari]
29-
- Version [e.g. 22]
30-
31-
**Smartphone (please complete the following information):**
32-
- Device: [e.g. iPhone6]
33-
- OS: [e.g. iOS8.1]
34-
- Browser [e.g. stock browser, safari]
35-
- Version [e.g. 22]
36-
37-
**Additional context**
38-
Add any other context about the problem here.
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what the bug is.
12+
13+
**To Reproduce**
14+
Steps to reproduce the behavior:
15+
1. Go to '...'
16+
2. Click on '....'
17+
3. Scroll down to '....'
18+
4. See error
19+
20+
**Expected behavior**
21+
A clear and concise description of what you expected to happen.
22+
23+
**Screenshots**
24+
If applicable, add screenshots to help explain your problem.
25+
26+
**Desktop (please complete the following information):**
27+
- OS: [e.g. iOS]
28+
- Browser [e.g. chrome, safari]
29+
- Version [e.g. 22]
30+
31+
**Smartphone (please complete the following information):**
32+
- Device: [e.g. iPhone6]
33+
- OS: [e.g. iOS8.1]
34+
- Browser [e.g. stock browser, safari]
35+
- Version [e.g. 22]
36+
37+
**Additional context**
38+
Add any other context about the problem here.

.github/ISSUE_TEMPLATE/custom.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
1-
---
2-
name: Custom issue template
3-
about: Describe this issue template's purpose here.
4-
title: ''
5-
labels: ''
6-
assignees: ''
7-
8-
---
9-
10-
1+
---
2+
name: Custom issue template
3+
about: Describe this issue template's purpose here.
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,20 @@
1-
---
2-
name: Feature request
3-
about: Suggest an idea for this project
4-
title: ''
5-
labels: ''
6-
assignees: ''
7-
8-
---
9-
10-
**Is your feature request related to a problem? Please describe.**
11-
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12-
13-
**Describe the solution you'd like**
14-
A clear and concise description of what you want to happen.
15-
16-
**Describe alternatives you've considered**
17-
A clear and concise description of any alternative solutions or features you've considered.
18-
19-
**Additional context**
20-
Add any other context or screenshots about the feature request here.
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.

.github/workflows/test-package.yaml

Lines changed: 62 additions & 62 deletions
Original file line numberDiff line numberDiff line change
@@ -1,63 +1,63 @@
1-
# inspired by https://jacobian.org/til/github-actions-poetry/
2-
3-
on:
4-
push:
5-
branches: [main]
6-
pull_request:
7-
8-
env:
9-
POETRY_VERSION: 1.8.3
10-
FMP_API_KEY: ${{ secrets.FMP_API_KEY }}
11-
jobs:
12-
build:
13-
runs-on: ${{ matrix.os }}
14-
strategy:
15-
max-parallel: 1
16-
fail-fast: false
17-
matrix:
18-
python-version: ["3.12"]
19-
os: [ubuntu-latest, macOS-latest]
20-
env:
21-
POETRY_VIRTUALENVS_IN_PROJECT: true
22-
steps:
23-
- uses: actions/checkout@v3
24-
- uses: actions/setup-python@v5
25-
with:
26-
python-version: ${{ matrix.python-version }}
27-
28-
# Cache the installation of Poetry itself, e.g. the next step. This prevents the workflow
29-
# from installing Poetry every time, which can be slow. Note the use of the Poetry version
30-
# number in the cache key, and the "-0" suffix: this allows you to invalidate the cache
31-
# manually if/when you want to upgrade Poetry, or if something goes wrong.
32-
- name: cache poetry install
33-
uses: actions/cache@v4
34-
with:
35-
path: ~/.local
36-
key: poetry-cache-${{ runner.os }}-${{ matrix.python-version }}-${{ env.POETRY_VERSION }}
37-
38-
# Install Poetry. You could do this manually, or there are several actions that do this.
39-
# `snok/install-poetry` seems to be minimal yet complete, and really just calls out to
40-
# Poetry's default install script, which feels correct. I pin the Poetry version here
41-
# because Poetry does occasionally change APIs between versions and I don't want my
42-
# actions to break if it does.
43-
#
44-
# The key configuration value here is `virtualenvs-in-project: true`: this creates the
45-
# venv as a `.venv` in your testing directory, which allows the next step to easily
46-
# cache it.
47-
- uses: snok/install-poetry@v1
48-
with:
49-
version: 1.8.3
50-
virtualenvs-create: true
51-
virtualenvs-in-project: true
52-
53-
# Cache your dependencies (i.e. all the stuff in your `pyproject.toml`)
54-
- name: cache venv
55-
uses: actions/cache@v4
56-
with:
57-
path: .venv
58-
key: venv-${{ runner.os }}-${{ matrix.python-version }}-${{ hashFiles('**/poetry.lock') }}
59-
- run: poetry install --no-interaction --no-root
60-
if: steps.cache-deps.outputs.cache-hit != 'true'
61-
- run: poetry install --no-interaction
62-
- run: poetry run ruff check --fix
1+
# inspired by https://jacobian.org/til/github-actions-poetry/
2+
3+
on:
4+
push:
5+
branches: [main]
6+
pull_request:
7+
8+
env:
9+
POETRY_VERSION: 1.8.3
10+
FMP_API_KEY: ${{ secrets.FMP_API_KEY }}
11+
jobs:
12+
build:
13+
runs-on: ${{ matrix.os }}
14+
strategy:
15+
max-parallel: 1
16+
fail-fast: false
17+
matrix:
18+
python-version: ["3.12"]
19+
os: [ubuntu-latest, macOS-latest]
20+
env:
21+
POETRY_VIRTUALENVS_IN_PROJECT: true
22+
steps:
23+
- uses: actions/checkout@v3
24+
- uses: actions/setup-python@v5
25+
with:
26+
python-version: ${{ matrix.python-version }}
27+
28+
# Cache the installation of Poetry itself, e.g. the next step. This prevents the workflow
29+
# from installing Poetry every time, which can be slow. Note the use of the Poetry version
30+
# number in the cache key, and the "-0" suffix: this allows you to invalidate the cache
31+
# manually if/when you want to upgrade Poetry, or if something goes wrong.
32+
- name: cache poetry install
33+
uses: actions/cache@v4
34+
with:
35+
path: ~/.local
36+
key: poetry-cache-${{ runner.os }}-${{ matrix.python-version }}-${{ env.POETRY_VERSION }}
37+
38+
# Install Poetry. You could do this manually, or there are several actions that do this.
39+
# `snok/install-poetry` seems to be minimal yet complete, and really just calls out to
40+
# Poetry's default install script, which feels correct. I pin the Poetry version here
41+
# because Poetry does occasionally change APIs between versions and I don't want my
42+
# actions to break if it does.
43+
#
44+
# The key configuration value here is `virtualenvs-in-project: true`: this creates the
45+
# venv as a `.venv` in your testing directory, which allows the next step to easily
46+
# cache it.
47+
- uses: snok/install-poetry@v1
48+
with:
49+
version: 1.8.3
50+
virtualenvs-create: true
51+
virtualenvs-in-project: true
52+
53+
# Cache your dependencies (i.e. all the stuff in your `pyproject.toml`)
54+
- name: cache venv
55+
uses: actions/cache@v4
56+
with:
57+
path: .venv
58+
key: venv-${{ runner.os }}-${{ matrix.python-version }}-${{ hashFiles('**/poetry.lock') }}
59+
- run: poetry install --no-interaction --no-root
60+
if: steps.cache-deps.outputs.cache-hit != 'true'
61+
- run: poetry install --no-interaction
62+
- run: poetry run ruff check --fix
6363
- run: poetry run pytest

0 commit comments

Comments
 (0)