You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GiudGiud opened this issue
Dec 14, 2024
· 0 comments
Labels
P: normalA defect affecting operation with a low possibility of significantly affects.T: defectAn anomaly, which is anything that deviates from expectations.
It is very common to add "Function" or "Scaled" or "Parsed" in front of an object name to indicate the functionality has been augmented in a new object in an applicaiton.
However if the Moose documentation has a snippet like this:
!listing Object.C
this causes an ambiguity as both XYZObject.C and Object.C match the regex
Steps to Reproduce
Have two objects, one of them being named after the other with a prefix
Have a snippet / listing using the name of the other without the folder
Impact
Breaks doco on the application
[Optional] Diagnostics
No response
The text was updated successfully, but these errors were encountered:
GiudGiud
added
T: defect
An anomaly, which is anything that deviates from expectations.
P: normal
A defect affecting operation with a low possibility of significantly affects.
labels
Dec 14, 2024
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
Dec 14, 2024
P: normalA defect affecting operation with a low possibility of significantly affects.T: defectAn anomaly, which is anything that deviates from expectations.
Bug Description
It is very common to add "Function" or "Scaled" or "Parsed" in front of an object name to indicate the functionality has been augmented in a new object in an applicaiton.
However if the Moose documentation has a snippet like this:
!listing Object.C
this causes an ambiguity as both XYZObject.C and Object.C match the regex
Steps to Reproduce
Have two objects, one of them being named after the other with a prefix
Have a snippet / listing using the name of the other without the folder
Impact
Breaks doco on the application
[Optional] Diagnostics
No response
The text was updated successfully, but these errors were encountered: