Implement Italian Fiscal Code in Pascal
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker
- Domain
- backend
Research direction
Start with SPECIFICATION.md and the Python and PHP implementations under languages/. Create languages/pascal/ with the source, Dockerfile, run.sh, manifest.yaml and README.md, following the same layout. Done when ./elc test pascal passes 87/87 and the program reads one JSON object on stdin and writes the fiscal code as JSON on stdout.
Written by the indexing model from the issue text.
Description
Implement the Italian Fiscal Code algorithm in Pascal and get it verified by the shared test suite.
What to build
A program that reads one JSON object on stdin and writes the fiscal code (or an error) as JSON on stdout, exactly as described in SPECIFICATION.md.
$ echo '{"surname":"ROSSI","name":"MARIO","birth_date":"1980-01-01","sex":"M","birthplace_code":"H501"}' | ./elc run pascal
{"fiscal_code": "RSSMRA80A01H501U"}
Suggested setup
| Directory | languages/pascal/ |
| Family | historical |
| Docker base | debian:bookworm + fpc (just a suggestion) |
Checklist
-
languages/pascal/with source,Dockerfile,run.sh,manifest.yamlandREADME.md - The algorithm is written entirely in Pascal (no wrappers, no fiscal-code libraries, no remote calls)
-
./elc test pascalpasses 87/87 - PR opened with
Closes #<this issue>
See CONTRIBUTING.md and the Python / PHP implementations for complete examples.
🎃 This issue is part of Hacktoberfest. Comment below to claim it!
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openapi/every-language-fiscal-code
-
good first issue hacktoberfest help wanted new-language
Difficulty 2/5 Half a day Newbie friendliness 78/100
-
hacktoberfest help wanted historical-language new-language
Difficulty 3/5 1-2 days Newbie friendliness 70/100
-
hacktoberfest help wanted historical-language new-language
Difficulty 3/5 1-2 days Newbie friendliness 50/100
-
hacktoberfest help wanted historical-language new-language
Difficulty 4/5 3-5 days Newbie friendliness 50/100
-
hacktoberfest help wanted new-language
Difficulty 3/5 1-2 days Newbie friendliness 62/100
All issues in openapi/every-language-fiscal-code
Similar issues
-
comp/tools P2 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#142908 · 1 comment ·
-
[oblt-aw][autodoc] Fix malformed headings in new Buildkite docs pagesPossibly taken @github-actions claimed this today. Opendocumentation
Difficulty 1/5 Under an hour Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
[Bug]: fileUploadMatrix.test.ts URL case does a real DNS lookup and fails offlinePossibly taken @r2jaff claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ComposioHQ/composio#5054 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pytorch/tensordict#3286 ·
Maintainers usually reply within 1 day