Skip to content

Fix the path length limitation issue for example file names#2318

Merged
joelrosario merged 2 commits intomainfrom
fix-path-limit-issue
Mar 5, 2026
Merged

Fix the path length limitation issue for example file names#2318
joelrosario merged 2 commits intomainfrom
fix-path-limit-issue

Conversation

@StarKhan6368
Copy link
Copy Markdown
Contributor

What: Fix the path length limitation issue for example file names

Why: On Windows, file names are restricted to 255 characters, while the path length is limited to 260 characters. Similarly, on Unix systems, file names are also capped at 255 characters

How:

  • Prefers using operationId-status when feasible, which is also budgeted
  • Calculates the remaining budget, truncates the file name to ensure it stays within the specified limits, and appends a 6-character hash suffix to prevent any duplicates from overriding each other after budgeting

Checklist:

  • Unit Tests
  • Build passing locally
  • Sonar Quality Gate
  • Security scans don't report any vulnerabilities
  • Documentation added/updated (share link)
  • Sample Project added/updated (share link)
  • Demo video (share link)
  • Article on Website (share link)
  • Roadmpap updated (share link)
  • Conference Talk (share link)

- Add simple tests for the same
@StarKhan6368 StarKhan6368 force-pushed the fix-path-limit-issue branch 2 times, most recently from af3cd93 to af5aa48 Compare March 4, 2026 10:33
@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 4, 2026

Summary

Line coverage Branch coverage

Assembly Line coverage Branch coverage
application 63.2% 55.5%
application/backwardCompatibility 79.5% 65.1%
application/mcp 84.7% 76.9%
application/validate 1.2% 2.5%
io/specmatic/conversions 93.2% 78.7%
io/specmatic/conversions/lenient 97.6% 77.4%
io/specmatic/core 81.1% 62.7%
io/specmatic/core/azure 0% 0%
io/specmatic/core/config 60% 36%
io/specmatic/core/config/v1 97.9% 25%
io/specmatic/core/config/v2 91.9% 78.8%
io/specmatic/core/config/v3 55.6% 29.3%
io/specmatic/core/config/v3/components 78.9% 40%
io/specmatic/core/config/v3/components/runOptions 74.5% 45.5%
io/specmatic/core/config/v3/components/services 86.3% 58.5%
io/specmatic/core/config/v3/components/settings 100% 63.8%
io/specmatic/core/config/v3/components/sources 83.8% 61.5%
io/specmatic/core/config/v3/specmatic 57.6% 25%
io/specmatic/core/discriminator 52.6% 50%
io/specmatic/core/examples/module 45.7% 28.9%
io/specmatic/core/examples/server 73.8% 36.8%
io/specmatic/core/filters 83.1% 72.1%
io/specmatic/core/fuzzy 97.3% 93.8%
io/specmatic/core/git 9% 10.8%
io/specmatic/core/jsonoperator 67.4% 68.8%
io/specmatic/core/jsonoperator/value 86.2% 74.4%
io/specmatic/core/lifecycle 0% ****
io/specmatic/core/log 75.9% 62.3%
io/specmatic/core/matchers 78.4% 65.4%
io/specmatic/core/overlay 87.3% 58.8%
io/specmatic/core/pattern 87.3% 76.7%
io/specmatic/core/pattern/config 100% ****
io/specmatic/core/pattern/regex 94.5% 86.1%
io/specmatic/core/report 97.5% 91.6%
io/specmatic/core/route/modules 95% 87.5%
io/specmatic/core/utilities 69.5% 61.1%
io/specmatic/core/value 82.4% 69.2%
io/specmatic/core/wsdl/parser 81.4% 41%
io/specmatic/core/wsdl/parser/message 90% 72%
io/specmatic/core/wsdl/parser/operation 100% 100%
io/specmatic/core/wsdl/payload 81.1% 50%
io/specmatic/junit5/support 0% ****
io/specmatic/loader 84.6% 53.5%
io/specmatic/mcp/constants 0% ****
io/specmatic/mcp/report 0% 0%
io/specmatic/mcp/test 0% 0%
io/specmatic/mcp/test/client 0% 0%
io/specmatic/mcp/test/client/model 0% 0%
io/specmatic/mock 61.4% 56.5%
io/specmatic/proxy 67% 52%
io/specmatic/specmatic/core 100% ****
io/specmatic/specmatic/executable 100% ****
io/specmatic/specmatic/mcp 0% ****
io/specmatic/stub 79.8% 70%
io/specmatic/stub/listener 100% 100%
io/specmatic/stub/report 100% 77%
io/specmatic/test 73.8% 64.5%
io/specmatic/test/asserts 95.2% 86.6%
io/specmatic/test/handlers 89.7% 63.3%
io/specmatic/test/listeners 86.4% 53.2%
io/specmatic/test/reports 60% 33.3%
io/specmatic/test/reports/coverage 97.2% 54.9%
io/specmatic/test/reports/coverage/console 90.2% 84%
io/specmatic/test/reports/coverage/html 0% 0%
io/specmatic/test/reports/renderers 21.8% 24.1%
io/specmatic/test/utils 92.3% 80%

@StarKhan6368 StarKhan6368 force-pushed the fix-path-limit-issue branch from af5aa48 to 69490d3 Compare March 4, 2026 11:34
- Fix example name assertions, now contains contentType
@StarKhan6368 StarKhan6368 force-pushed the fix-path-limit-issue branch from 69490d3 to 8ddb5c9 Compare March 4, 2026 11:35
@joelrosario joelrosario self-requested a review March 5, 2026 06:51
@joelrosario joelrosario merged commit 66ee83f into main Mar 5, 2026
3 checks passed
@joelrosario joelrosario deleted the fix-path-limit-issue branch March 5, 2026 06:52
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