jalo classes in src should not be ignored
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- git
- Domain
- build-system
Research direction
Start with the repository's .gitignore and locate the rule that excludes Jalo classes under src. Check how those exclusions affect top-level Jalo classes and generated Jalo super classes when switching branches. Done means the relevant classes are no longer ignored and branch changes can compile without missing classes.
Written by the indexing model from the issue text.
Description
The .gitignore file should not ignore jalo classes in src as historically these classes were used to implement custom before Service Layer was introduced.
Besides this can break the compilation when switching to branches that don't have the item type due to the top level Jalo classes missing the generated Jalo super classes
- Dominant language
- TypeScript
- Stars
- 110
- Forks
- 199
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 SAP-samples/cloud-commerce-sample-setup
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
SAP-samples/cloud-commerce-sample-setup#128 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in SAP-samples/cloud-commerce-sample-setup
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JoviDeCroock/pracht#432 ·
Maintainers usually reply within 1 day
-
approved check:passed streams:add
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Hardware attribute name "app Connection Support" has inconsistent casingPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
walletbeat/walletbeat#1628 ·
Maintainers usually reply within 1 day
-
bug go
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
genkit-ai/genkit#6761 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NousResearch/hermes-agent#136483 ·
Maintainers usually reply within 1 day