Implement Italian Fiscal Code in COBOL
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 50/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker, json
- Domain
- backend
Research direction
Read SPECIFICATION.md and the Python and PHP implementations under languages/ to learn the fiscal code rules and the stdin/stdout JSON contract. Create languages/cobol/ with the source, Dockerfile, run.sh, manifest.yaml and README.md, following those examples. Done when ./elc test cobol passes all 87 cases and the algorithm is written entirely in COBOL.
Written by the indexing model from the issue text.
Description
Implement the Italian Fiscal Code algorithm in COBOL 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 cobol
{"fiscal_code": "RSSMRA80A01H501U"}
Suggested setup
| Directory | languages/cobol/ |
| Family | historical |
| Docker base | debian:bookworm + gnucobol (just a suggestion) |
Checklist
-
languages/cobol/with source,Dockerfile,run.sh,manifest.yamlandREADME.md - The algorithm is written entirely in COBOL (no wrappers, no fiscal-code libraries, no remote calls)
-
./elc test cobolpasses 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
- 0
- 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 65/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 new-language
Difficulty 3/5 1-2 days Newbie friendliness 62/100
All issues in openapi/every-language-fiscal-code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
collective/icalendar#1968 · 1 comment ·
Maintainers usually reply within 1 day
-
Deferred from #1869: Complete the companion pytest guardrail update noted in the PR description...Open
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#140958 ·
Maintainers usually reply within 1 day
-
Bug triage/confirmed
Difficulty 2/5 Half a day Newbie friendliness 85/100
agentscope-ai/agentscope#3355 ·
Maintainers usually reply within 2 days