Update docs about possible MOD files compilation errors with >=9.0#3106
Conversation
- Add table with all models and MOD files so that it would be easy for users to find the changed mod file. - Change version to >= 9.0 - Add link in the top level README fixes #1876
|
✔️ 775ec26 -> Azure artifacts URL |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3106 +/- ##
=======================================
Coverage 66.89% 66.89%
=======================================
Files 572 572
Lines 106664 106664
=======================================
Hits 71348 71348
Misses 35316 35316 ☔ View full report in Codecov by Sentry. |
This comment has been minimized.
This comment has been minimized.
|
✔️ ac53e5c -> Azure artifacts URL |
This comment has been minimized.
This comment has been minimized.
|
Is this just |
@1uc : this is only the user-facing parts and hence only C->C++ part for MOD files. |
|
@nrnhines: In issue #1876, we mentioned the following:
If this seems beneficial, one potential approach would be to display a message when *.cpp compilation fails in nrnivmodl (or at the end), such as:
Do you think this would be helpful for users, or could it become more of a distraction than an aid? |
Seems to me that that would be helpful. |
|
Please retry analysis of this Pull-Request directly on SonarCloud |
|
✔️ 2fcabe4 -> Azure artifacts URL |
Add a table with all models and MOD files so that it would be easy for users to find the changed mod file.
Change version to >= 9.0
Add a link in the top-level README
Check if we should add a link to docs if
nrnivmodlfails to compile.Changes
With this PR, in top level README me / RTD landing page we have
And the table in the main docs looks like
fixes #1876
Script used to generate table