Skip to content

compas_3dec development for compas_2 - #3

Merged
adellendice merged 35 commits into
mainfrom
wip_1
Aug 19, 2026
Merged

compas_3dec development for compas_2#3
adellendice merged 35 commits into
mainfrom
wip_1

Conversation

@adellendice

Copy link
Copy Markdown
Collaborator

What type of change is this?

  • Bug fix in a backwards-compatible manner.
  • New feature in a backwards-compatible manner.
  • Breaking change: bug fix or new feature that involve incompatible API changes.
  • Other (e.g. doc update, configuration, etc)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • I added a line to the CHANGELOG.md file in the Unreleased section under the most fitting heading (e.g. Added, Changed, Removed).
  • I ran all tests on my computer and it's all green (i.e. invoke test).
  • I ran lint on my computer and there are no errors (i.e. invoke lint).
  • I added new functions/classes and made them available on a second-level import, e.g. compas.datastructures.Mesh.
  • I have added tests that prove my fix is effective or that my feature works.
  • I have added necessary documentation (if appropriate)

@petrasvestartas

Copy link
Copy Markdown
Collaborator

@adellendice I added minimal changes to the file problem_example.py to be compatible with the new model update.

@adellendice
adellendice merged commit 314138f into main Aug 19, 2026
2 of 5 checks passed
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