clipper2 0.6.0

A safe, idiomatic Rust API for 2D polygon boolean clipping (intersection, union, difference, XOR), offsetting (inflate/deflate), Minkowski sum/difference, simplification, area, and point-in-polygon, on top of Clipper2.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67

# git-cliff configuration
# https://git-cliff.org/docs/configuration

[changelog]
header = """
# Changelog

All notable changes to this project will be documented in this file.

"""
body = """
{%- if version %}
### [{{ version | trim_start_matches(pat="v") }}]\
(https://github.com/tirithen/clipper2/compare/{{ previous.version }}...{{ version }}) \
({{ timestamp | date(format="%Y-%m-%d") }})
{%- else %}
### Unreleased
{%- endif %}
{% for group, commits in commits | group_by(attribute="group") %}
### {{ group }}

{% for commit in commits -%}
* {{ commit.message }} \
([{{ commit.id | truncate(length=7, end="") }}]\
(https://github.com/tirithen/clipper2/commit/{{ commit.id }}))
{% endfor %}
{%- endfor %}
"""
footer = ""
trim = true

[git]
conventional_commits = true
filter_unconventional = true
filter_commits = false
tag_pattern = "v[0-9].*"
sort_commits = "oldest"
commit_parsers = [
  # The BREAKING-CHANGE footer rule deliberately precedes the message
  # rules: a commit can only land in one group, and a release-defining
  # breaking change deserves its own section regardless of whether the
  # subject prefix is feat / fix / refactor / etc.
  { footer = "(?i)^breaking[ -]change", group = "BREAKING CHANGES" },
  { message = "^feat", group = "Features" },
  { message = "^fix", group = "Bug Fixes" },
  { message = "^perf", group = "Performance Improvements" },
  { message = "^revert", group = "Reverts" },
  { message = "^doc", skip = true },
  { message = "^style", skip = true },
  { message = "^refactor", skip = true },
  { message = "^test", skip = true },
  { message = "^chore", skip = true },
  { message = "^ci", skip = true },
  { message = "^build", skip = true },
]

[remote.github]
owner = "tirithen"
repo = "clipper2"

[bump]
# Honour pre-1.0 SemVer (the Rust / Cargo convention): for 0.x.y the
# 'x' position is the breaking axis, so a BREAKING CHANGE bumps the
# minor (0.5.4 -> 0.6.0), not the major. A 'feat' on 0.x is treated
# as a non-breaking addition and bumps the patch.
breaking_always_bump_major = false
features_always_bump_minor = false