Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / mit-cml/blockly-plugins issues and pull requests

#50 - Fix plugin import in usage instructions

Pull Request - State: closed - Opened by pavi2410 6 months ago - 1 comment

#48 - Name problems

Issue - State: open - Opened by SebCanet 7 months ago - 6 comments

#47 - support unpkg way use this plugin

Issue - State: closed - Opened by mlzboy 8 months ago - 2 comments

#46 - Add documentation on how to use use the fields to define your own blocks

Issue - State: open - Opened by mark-friedman 8 months ago
Labels: documentation, lexical variables

#45 - Refactor the plugin to use the lexical variable mixin from App Inventor

Issue - State: open - Opened by mark-friedman 8 months ago - 1 comment
Labels: enhancement, lexical variables

#44 - Add documentation in the README for the core, blocks and generators imports

Issue - State: open - Opened by mark-friedman 8 months ago
Labels: documentation, lexical variables

#44 - Add documentation in the README for the core, blocks and generators imports

Issue - State: open - Opened by mark-friedman 8 months ago
Labels: documentation, lexical variables

#43 - Add lexical variable getter and setter blocks to core

Issue - State: open - Opened by mark-friedman 8 months ago
Labels: enhancement, lexical variables

#42 - Export NameSet and Substitution classes

Pull Request - State: closed - Opened by ewpatton 9 months ago

#41 - Changes to support use of the plugin by App Inventor

Pull Request - State: closed - Opened by mark-friedman 12 months ago

#40 - Support different gestures on touch devices

Issue - State: open - Opened by ewpatton 12 months ago

#38 - Have trouble using plugin in typescript project

Issue - State: open - Opened by chi-w-ng about 1 year ago - 3 comments

#37 - Implement indented inputs for lexvar plugin

Pull Request - State: closed - Opened by ewpatton about 1 year ago
Labels: enhancement

#37 - Implement indented inputs for lexvar plugin

Pull Request - State: closed - Opened by ewpatton about 1 year ago
Labels: enhancement

#36 - Make this plugin compatible with Blockly 10

Issue - State: closed - Opened by pierrickgrand about 1 year ago - 4 comments

#35 - Global_ Declaration 'should allow magnetic attraction to make them look more neat

Issue - State: open - Opened by Small-Shu about 1 year ago
Labels: enhancement, lexical variables

#33 - Add components for testing

Pull Request - State: closed - Opened by mark-friedman about 1 year ago

#32 - Update to Blockly v10

Pull Request - State: closed - Opened by ewpatton about 1 year ago - 8 comments

#31 - Update Blockly imports to make dist package smaller

Pull Request - State: closed - Opened by ewpatton over 1 year ago - 1 comment

#30 - Make flydowns use the same renderer as the target workspace

Pull Request - State: closed - Opened by SneezingCactus over 1 year ago - 2 comments

#28 - Func statement solution

Pull Request - State: open - Opened by marktohark about 2 years ago - 2 comments

#27 - Support non-default renderers

Issue - State: closed - Opened by lukeplays33 about 2 years ago - 3 comments

#25 - What is the minimum requirement to make a block lexical-variable compatible?

Issue - State: closed - Opened by ysfchn over 2 years ago - 8 comments

#24 - flydown does not accept custom block colours

Issue - State: closed - Opened by lukeplays33 over 2 years ago - 9 comments

#22 - global variables dropdown should check for all blocks instead of only top blocks

Issue - State: open - Opened by lukeplays33 over 2 years ago - 3 comments
Labels: enhancement, lexical variables

#21 - Block outside of parent statment input dont show an warning

Issue - State: closed - Opened by lukeplays33 almost 3 years ago - 3 comments

#20 - Variable dropdown sould show lexical variables

Issue - State: closed - Opened by lukeplays33 almost 3 years ago - 11 comments

#19 - Fix codegen for proc calls and loops

Pull Request - State: closed - Opened by mark-friedman almost 3 years ago

#16 - Write documentation to show developers how to create their own blocks based on the fields defined here

Issue - State: open - Opened by mark-friedman almost 3 years ago
Labels: documentation, lexical variables

#15 - You have to click outside the block to get warning indicator removed after variable rename

Issue - State: open - Opened by mark-friedman almost 3 years ago - 4 comments
Labels: bug, enhancement, lexical variables

#14 - Fixed homepage URL

Pull Request - State: closed - Opened by seldomU almost 3 years ago - 1 comment

#13 - Create plugin for App Inventor style warning/error handler

Issue - State: open - Opened by mark-friedman about 3 years ago
Labels: enhancement

#12 - Variable name checker should be an init option

Issue - State: open - Opened by mark-friedman about 3 years ago
Labels: enhancement, lexical variables

#11 - Split into a fields plugin and a blocks plugin

Issue - State: open - Opened by mark-friedman about 3 years ago
Labels: enhancement, lexical variables

#10 - Allow new blocks to be created by developers based on the new fields

Issue - State: closed - Opened by mark-friedman about 3 years ago - 1 comment
Labels: enhancement, lexical variables

#9 - Maybe remove FieldLexicalVariable.block_

Issue - State: open - Opened by mark-friedman about 3 years ago - 6 comments
Labels: enhancement, good first issue, lexical variables

#8 - Remove the code which we added that calls getOptions() to regenerate the options cache

Issue - State: open - Opened by mark-friedman about 3 years ago
Labels: enhancement, lexical variables

#7 - Reduce the number of imports in index.js

Issue - State: open - Opened by mark-friedman about 3 years ago
Labels: enhancement, lexical variables

#6 - Make FieldLexicalVariable use FieldNoCheckDropdown

Issue - State: open - Opened by mark-friedman about 3 years ago
Labels: enhancement, lexical variables

#5 - Add a new renderer that implements appendIndentedValueInput

Issue - State: open - Opened by mark-friedman about 3 years ago
Labels: enhancement, lexical variables

#4 - Maybe use the Blockly ConnectionChecker interface to enforce variable scope rules.

Issue - State: open - Opened by mark-friedman about 3 years ago
Labels: enhancement, lexical variables

#3 - Should we disable invalid variable setters and getters?

Issue - State: open - Opened by mark-friedman about 3 years ago
Labels: enhancement, good first issue, lexical variables

#2 - Write some tests!

Issue - State: open - Opened by mark-friedman about 3 years ago
Labels: enhancement, lexical variables

#1 - Create an option to disable local variables to shadow globals

Issue - State: open - Opened by mark-friedman about 3 years ago
Labels: enhancement, good first issue, lexical variables