-
Notifications
You must be signed in to change notification settings - Fork 3.8k
fix!: fix or silence type errors #6105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
bb6fe55
587b846
3ef2e99
5ce92eb
a2a32a3
4183917
93ef7bd
228a3a6
e902c1c
122026c
f449961
91e859f
773be62
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -198,4 +198,19 @@ IFlyout.prototype.position; | |
| */ | ||
| IFlyout.prototype.isDragTowardWorkspace; | ||
|
|
||
| /** | ||
| * Does this flyout allow you to create a new instance of the given block? | ||
| * Used for deciding if a block can be "dragged out of" the flyout. | ||
| * @param {!BlockSvg} block The block to copy from the flyout. | ||
| * @return {boolean} True if you can create a new instance of the block, false | ||
| * otherwise. | ||
| * @package | ||
| */ | ||
| IFlyout.prototype.isBlockCreatable; | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is removing the underscore on this name a breaking change? I still don't understand our policy on external developers overriding
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Technically a breaking change, so I renamed the PR to
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. And also added a comment on the breaking change to the PR description. |
||
|
|
||
| /** | ||
| * Scroll the flyout to the beginning of its contents. | ||
| */ | ||
| IFlyout.prototype.scrollToStart; | ||
|
|
||
| exports.IFlyout = IFlyout; | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -82,4 +82,19 @@ IToolboxItem.prototype.isCollapsible; | |
| */ | ||
| IToolboxItem.prototype.dispose; | ||
|
|
||
| /** | ||
| * Gets the HTML element that is clickable. | ||
| * @return {?Element} The HTML element that receives clicks. | ||
| * @public | ||
| */ | ||
| IToolboxItem.prototype.getClickTarget; | ||
|
|
||
| /** | ||
| * Sets whether the category is visible or not. | ||
| * For a category to be visible its parent category must also be expanded. | ||
| * @param {boolean} isVisible True if category should be visible. | ||
| * @protected | ||
| */ | ||
| IToolboxItem.prototype.setVisible_; | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this supposed to exist here? Or on the collapsible toolbox item interface?
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It has to move all the way up to IToolboxItem because of how it's being used. @alschmiedt said that "we allow any toolbox item to be in a collapsible category" and that it should be left as is for compatibility reasons. But I noted it in my issue for follow-ups, in case we can find a better way to deal with it before the next release. |
||
|
|
||
| exports.IToolboxItem = IToolboxItem; | ||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are workspace comments bubbles? That seems like not what they are.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Notes for the curious:
I think it's just to make workspace comments similar to block comments. And block comments are icons/bubbles, just like mutators.
Bubbles sit on a different canvas than blocks, and always on top. They do that so that blocks on the workspace can never look like they're inside an open mutator.