Skip to content

Fix potential typo issue in RSTAB Python Client#42

Open
vemlor-bot wants to merge 1 commit into
dlubal-software:mainfrom
vemlor-bot:vemlor/fix-issue-40-bug-potential-typo-in-this-
Open

Fix potential typo issue in RSTAB Python Client#42
vemlor-bot wants to merge 1 commit into
dlubal-software:mainfrom
vemlor-bot:vemlor/fix-issue-40-bug-potential-typo-in-this-

Conversation

@vemlor-bot

Copy link
Copy Markdown

Two ResultTables methods call SOAP operations with a misspelled name:

  • line 328 — get_results_for_efeective_lengths_and_critical_loads_by_eigenvector
  • line 355 — get_results_for_efeective_lengths_and_critical_loads_by_member

The RSTAB WebService contract spells these ..._effective_... (see IRstabModel.cs in Dlubal_CSharp_Client):

get_results_for_effective_lengths_and_critical_loads_by_eigenvector
get_results_for_effective_lengths_and_critical_loads_by_member

So the misspelled client calls target SOAP operations that don't exist — both methods fail at runtime for anyone who calls them. This corrects the spelling to match the service contract; no behaviour change beyond making the two methods reachable.

Closes #40


Opened by Vemlor. We watch public CI, prep the fix, and send it as a ready-to-merge PR. Fully automated and unsolicited; close it with no hard feelings if you'd rather not. Happy to adjust anything.

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.

BUG: Potential typo

1 participant