-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Correct file path management #125
Conversation
Job Precheck on 1944998 wanted to post the following: Your code requires style changes. A patch was auto generated and copied here
Alternatively, with your repository up to date and in the top level of your repository:
|
1944998
to
451c24f
Compare
ca1cc7d
to
3960547
Compare
@cticenhour this is ready for review. Zapdos passes all tests with shannon-lab/zapdos#240. |
3960547
to
a26869d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great line reduction!
Test results: https://civet.inl.gov/pr/21435/ |
Co-authored-by: Casey Icenhour <cticenhour@gmail.com>
Co-authored-by: Casey Icenhour <cticenhour@gmail.com>
6511121
to
8ecb734
Compare
refs idaholab/moose#26947
Requires idaholab/moose#27143 and is in support of idaholab/moose#26947
All
file_location
parameters are set to theFileName
type, which eventually will be auto filled with the correct absolute path to the file base. For objects that have a default, the default is set to.
(cwd of the input file). Allproperty_file
parameters are set to theRelativeFileName
type, which means don't have their absolute paths resolved so you can do<file_location>/<property_file>
.