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
The toHtml output for the x12 file needs some simple changes to make it easy to use in an application to support an online Edit form.
The id attribute of each loop/segment/element (which is a machine readable "path" to the x12 entity in the document) should include itself. Previously it only included it's parents, which was a bug.
Each loop/segment/element should have a title attribute containing a human readable "path" to the x12 entity.
For supporting multi-claim 837's, need a toHtml method that takes a data loop index.
And each data loop needs to be in a
container with an ID to identify what data loop it belongs to. This allows a nice paging ability.
Add a class on the input text field for elements for each of css selectors
The text was updated successfully, but these errors were encountered:
nddipiazza
added a commit
to nddipiazza/x12-parser
that referenced
this issue
Jul 12, 2020
The toHtml output for the x12 file needs some simple changes to make it easy to use in an application to support an online Edit form.
id
attribute of each loop/segment/element (which is a machine readable "path" to the x12 entity in the document) should include itself. Previously it only included it's parents, which was a bug.title
attribute containing a human readable "path" to the x12 entity.data loop index
.The text was updated successfully, but these errors were encountered: