Skip to content

Spline Parser Rule Consistency#3562

Closed
erslavin wants to merge 1 commit intoPixarAnimationStudios:devfrom
NVIDIA-Omniverse:pegtl_spline_patch
Closed

Spline Parser Rule Consistency#3562
erslavin wants to merge 1 commit intoPixarAnimationStudios:devfrom
NVIDIA-Omniverse:pegtl_spline_patch

Conversation

@erslavin
Copy link
Copy Markdown
Contributor

@erslavin erslavin commented Mar 6, 2025

Description of Change(s)

  • Modified a few parser rules for spline data to make consistent with goals of internal vs. external padding
  • Aligned comments above rules to better represent rule intent
  • Removed multiline spacing between knot parameters in favor of token separators
  • Replaced inline padding with token separator to better describe whitespace intent
  • Added additional tests for incorrect spline parsing rules

Link to proposal (if applicable)

Fixes Issue(s)

Checklist

- Modified a few parser rules for spline data to make consistent
  with goals of internal vs. external padding
- Aligned comments above rules to better represent rule intent
- Removed multiline spacing between knot parameters in favor of
  token separators
- Replaced inline padding with token separator to better describe
  whitespace intent
- Added additional tests for incorrect spline parsing rules
@asluk asluk added the needs review Issue needing input/review by the repo maintainer (Pixar) label Mar 6, 2025
@jesschimein
Copy link
Copy Markdown
Collaborator

Filed as internal issue #USD-10751

(This is an automated message. See here for more information.)

@jesschimein
Copy link
Copy Markdown
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

@pixar-oss pixar-oss closed this in d2f309c Mar 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs review Issue needing input/review by the repo maintainer (Pixar)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants