Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

✨ Produce "//" in web paths #4935

Merged
merged 5 commits into from
Apr 26, 2024
Merged

✨ Produce "//" in web paths #4935

merged 5 commits into from
Apr 26, 2024

Conversation

dubzzz
Copy link
Owner

@dubzzz dubzzz commented Apr 26, 2024

Even if it used to be already the case, users had to specify a larger than default size to be able to see paths containing a "//" into them. As "//" is crucial in paths and totally part of the spec, they need to be generated with our default size too.

The current PR makes sure we have a better balance between number of segments in a path and length of the segments. Our previous version (with default size) used to sacrify the number of segments and to prefer longer one. We now mix both.

Related to #4896

Category:

  • ✨ Introduce new features
  • 📝 Add or update documentation
  • ✅ Add or update tests
  • 🐛 Fix a bug
  • 🏷️ Add or update types
  • ⚡️ Improve performance
  • Other(s): ...

Potential impacts:

  • Generated values: anything related on web-path
  • Shrink values: anything related on web-path
  • Performance: anything related on web-path might be slightly slower, but probably unnoticeable
  • Typings
  • Other(s): ...

Even if it used to be already the case, users had to specify a larger than default size to be able to see paths containing a "//" into them. As "//" is crucial in paths and totally part of the spec, they need to be generated with our default size too.

The current PR makes sure we have a better balance between number of segments in a path and length of the segments. Our previous version (with default size) used to sacrify the number of segments and to prefer longer one. We now mix both.

Related to #4896
Copy link

codesandbox-ci bot commented Apr 26, 2024

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 494f5a6:

Sandbox Source
@fast-check/examples Configuration

Copy link
Contributor

👋 A preview of the new documentation is available at: http://662b575b8b83d48537252a61--dubzzz-fast-check.netlify.app

Copy link

codecov bot commented Apr 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.87%. Comparing base (1dbbac8) to head (494f5a6).
Report is 4 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4935   +/-   ##
=======================================
  Coverage   96.87%   96.87%           
=======================================
  Files         213      213           
  Lines       16283    16296   +13     
  Branches     2664     2667    +3     
=======================================
+ Hits        15774    15787   +13     
  Misses        509      509           
Flag Coverage Δ
unit-tests 96.87% <100.00%> (+<0.01%) ⬆️
unit-tests-18.x-Linux 96.87% <100.00%> (+<0.01%) ⬆️
unit-tests-20.x-Linux 96.87% <100.00%> (+<0.01%) ⬆️
unit-tests-22.x-Linux 96.87% <100.00%> (+<0.01%) ⬆️
unit-tests-latest-Linux 96.87% <100.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

@dubzzz dubzzz merged commit 043d6ef into main Apr 26, 2024
76 checks passed
@dubzzz dubzzz deleted the segments branch April 26, 2024 08:40
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.

1 participant