Skip to content

Document all Pico formatting rules - #2939

Open
toinehartman wants to merge 1 commit into
mainfrom
fix/pico-formatter-options
Open

toinehartman wants to merge 1 commit into
mainfrom
fix/pico-formatter-options

Conversation

@toinehartman

@toinehartman toinehartman commented Oct 19, 2026 •

Copy link
Copy Markdown
Member

Document some undocumented formatter rules, so the respective page on the website is more accurate.

@toinehartman toinehartman self-assigned this Oct 19, 2026
@codecov

codecov Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 45%. Comparing base (7860c84) to head (536b5e2).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##              main   #2939   +/-   ##
=======================================
- Coverage       45%     45%   -1%     
  Complexity    6815    6815           
=======================================
  Files          844     844           
  Lines        68823   68823           
  Branches     10038   10038           
=======================================
- Hits         31432   31423    -9     
- Misses       34995   35004    +9     
  Partials      2396    2396           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@jurgenvinju

Copy link
Copy Markdown
Member

Maybe we should move all of pico under the demo folder? The tutor compiler will show all the bodies of functions as well for modules under a demo folder. So: demo::lang::pico instead of lang::pico

Comment thread src/org/rascalmpl/library/lang/pico/format/Formatting.rsc Outdated

@jurgenvinju jurgenvinju left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better demonstrate without the opts for toBox since that is almost a noop for most languages and a lot of wiring for every recursive call.

@toinehartman toinehartman changed the title Pass all options to Pico formatter Document all Pico formatting rules Oct 23, 2026
@toinehartman
toinehartman force-pushed the fix/pico-formatter-options branch from ac97db1 to 536b5e2 Compare October 23, 2026 12:59
@sonarqubecloud

Copy link
Copy Markdown

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants