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
It caused errors when adding the paragraph grammar, then once added and saved, it causes catastrophic failure (see stacktrace below)
I have one IGrammar method using Paragraph with x += this["TableMethod"].
I have the TableMethod IGrammar using either this["Item"].AsTable("Table") or using CreateNewObject(...).AsTable("Table"). Both fail with this issue.
Tested with various recent versions, still fails with Storyteller Version=4.3.1 and dotnet-storyteller Version=1.1.2
TypeError: this.children[0].selectFirst is not a function
at Paragraph.selectFirst (paragraph.js:159)
at Paragraph.selectFirst (paragraph.js:159)
at Step.selectFirst (step.js:205)
at Section.StepHolder.self.selectFirst (step-holder.js:158)
at SpecificationNavigator.moveFirst (specification-navigator.js:86)
at new Specification (specification.js:342)
at new SpecRecord (spec-record.js:33)
at eval (hierarchy-loaded.js:12)
at Array.forEach (<anonymous>)
at HierarchyLoaded (hierarchy-loaded.js:11)
hmmm, i may have been seeing two instances of the same bug in two places.
I suggest investigation around CreateNewObject inside a Grammar, used inside a paragraph potentially causing the above. It looks from above that the this is the grammar, inside the paragraph, but the this.children[0] is the silent grammar from _.ObjectIs = c => new T(); inside CreateNewObject (
It caused errors when adding the paragraph grammar, then once added and saved, it causes catastrophic failure (see stacktrace below)
I have one
IGrammar
method usingParagraph
withx += this["TableMethod"]
.I have the TableMethod
IGrammar
using eitherthis["Item"].AsTable("Table")
or usingCreateNewObject(...).AsTable("Table")
. Both fail with this issue.Tested with various recent versions, still fails with
Storyteller Version=4.3.1
anddotnet-storyteller Version=1.1.2
(Possibly related to #415)
The text was updated successfully, but these errors were encountered: