Compliance - Inconsistent Namespaces and ErrorLog #216
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issues addressed by this PR
Two compliance issues:
Closes #215
Closes #219
Capitalized all instances of ETABS, except those which are in PascalCase/camelCase, i.e. object names. Maybe we should hit those too?
Changelog
Etabs
namespaces where not all cap, so they are allETABS
; only exceptions are those things that want PascalCase/camelCase (i.e. object names)ErrorLog
to use Reflection.RecordErrorGetNextIdOfType()
which is no longer used becauseNextId()
has been disabled.