Skip to content

Conversation

sderazo
Copy link

@sderazo sderazo commented Aug 21, 2025

The change from changesForModelModication() to changesForModelModification() (originally declared in the PDEModelUtility.java file) is being made to improve the coding and debugging experience for developers. One of the parameters that this function takes in is final ModelModification modification, which makes me think that Modication should be Modification instead. This would help save time with debugging since when I was working on Issue 1813, I saw that there was an error message with the function and I could not figure out what was wrong until I saw that I misspelled the function by one letter.

The change from changesForModelModication() to changesForModelModification() (originally declared in the PDEModelUtility.java file) is being made to improve the coding and debugging experience for developers. One of the parameters that this function takes in is final ModelModification modification, which makes me think that Modication should be Modification instead. This would help save time with debugging since when I was working on Issue 1813, I saw that there was an error message with the function and I could not figure out what was wrong until I saw that I misspelled the function by one letter.
Copy link

Test Results

  618 files  ±0    618 suites  ±0   49m 23s ⏱️ - 5m 47s
3 611 tests ±0  3 556 ✅ ±0   54 💤 ±0  1 ❌ ±0 
8 183 runs  ±0  8 043 ✅ ±0  139 💤 ±0  1 ❌ ±0 

For more details on these failures, see this check.

Results for commit ed7ee34. ± Comparison against base commit d9ad053.

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