Feature #21659

Redesign the output from the Javascript generator.

Added by Richard Neswold almost 2 years ago. Updated about 1 year ago.

Javascript Generator
Target version:
Start date:
Due date:
% Done:


Estimated time:
(Total: 0.00 h)


Now that we've gained experience with Javascript, there are a few changes we should make to the generator's output. Some ideas:

  • Use the class syntax for the request and reply messages rather than the older, function syntax.
  • The Javascript should use generators instead of the custom object.
  • In the Request class hierarchy, we should add a (static?) method that returns the function that unmarshals replies. This way, when the ACNET module marshals an outgoing message, it can deliver an unmarshalled reply.
  • The generator should emit Typescript code or, at the very least, Typescript declaration files. (done: 264e5fcc)

When tackling these features, please create a subtask that focuses only on it.


Feature #21660: Use class syntax for request, reply, and structs in Javascript generatorNew

Feature #22256: Use generators in Javascript output.ClosedRichard Neswold


#1 Updated by Richard Neswold almost 2 years ago

  • Due date set to 01/11/2019

due to changes in a related task: #21660

#2 Updated by Richard Neswold over 1 year ago

  • Due date set to 04/01/2019

due to changes in a related task: #22256

#3 Updated by Richard Neswold over 1 year ago

  • Tracker changed from Support to Feature

#4 Updated by Richard Neswold over 1 year ago

  • Target version deleted (Protocol Compiler v1.2)
  • Assignee deleted (Richard Neswold)
  • Description updated (diff)

Remove "Target version" since this issue is a catch-all for subtasks that modify the Javascript generator and it might survive across releases of the protocol compiler.

#5 Updated by Richard Neswold about 1 year ago

  • Description updated (diff)

Added: 264e5fcc

Added this 5 months ago, but forgot to update this issue.

Also available in: Atom PDF