Skip to content

Conversation

@ivaylo-matov
Copy link
Contributor

Purpose

This PR aims to addressDYN-8595.

Curve Mapper now supports a list of doubles to unevenly distribute points along the selected curve.

DYN-8595-Draft

Declarations

Check these if you believe they are true

  • The codebase is in a better state after this PR
  • Is documented according to the standards
  • The level of testing this PR includes is appropriate
  • User facing strings, if any, are extracted into *.resx files
  • All tests pass using the self-service CI.
  • Snapshot of UI changes, if any.
  • Changes to the API follow Semantic Versioning and are documented in the API Changes document.
  • This PR modifies some build requirements and the readme is updated
  • This PR contains no files larger than 50 MB

Release Notes

Curve Mapper now supports a list of doubles to unevenly distribute points along the selected curve.

Reviewers

@QilongTang
@reddyashish
@zeusongit

FYIs

@achintyabhat
@dnenov

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

See the ticket for this pull request: https://jira.autodesk.com/browse/DYN-8595

@zeusongit zeusongit added this to the 3.5 milestone Mar 31, 2025
@reddyashish
Copy link
Collaborator

Conflicts here.

private readonly AssociativeNode pointsCountDefaultValue =
AstFactory.BuildExprList(new List<AssociativeNode>
{
AstFactory.BuildDoubleNode(pointCountDefaultValue)
Copy link
Collaborator

Choose a reason for hiding this comment

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

The pointsCount will always be int right? why use the double node?

Copy link
Collaborator

Choose a reason for hiding this comment

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

oh, is it to support a list of doubles too.

@reddyashish
Copy link
Collaborator

@avidit This smoke test SaveGraphAs.SaveGraphAs is failing here and i don't see any relevant changes. Is that test flaky or something we need to investigate?

@reddyashish
Copy link
Collaborator

Closing this as these changes are in #16078

@reddyashish reddyashish closed this Apr 3, 2025
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.

3 participants