refactor(generators): Introduce DartGenerator
class, Order
enum
#7160
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.
The basics
npm run format
andnpm run lint
The details
Resolves
Part of #7085.
Proposed Changes
Introduce a
DartGenerator
class to be the class of whichdartGenerator
is an instance (without any additional properties making it a singleton).Introduce an
Order
enum (for now Closure-style) for the operator precedence table.Don't rename
dartGenerator
toDart
in generators/dart/*.js.Behaviour Before/After Change
There should be no changes in behaviour.
Reason for Changes
See #7085.
Test Coverage
Passes
npm test
; no changes to manual testing anticipated.Documentation
Documentation for the
DartGenerator
class andOrder
enum should be automatically generated by our JSDoc configs.Additional Information
It is now possible to create multiple
dartGenerator
objects, which can share (or not share) block generator implementations. Note that new instances do not by default come with any generator functions pre-installed.We now provide an enum of the operator precedence values (order of operations) constants as a separate export:
DEPRECATION: The
.ORDER_*
constants ondartGenerator
are deprecated; they still exist but are no longer part of the documented API and will be removed in a future version of Blockly. We recommend that you update your custom generator code to use theOrder
enum at your earliest convenience.