Skip to content
This repository was archived by the owner on Jun 3, 2026. It is now read-only.

Clean up block config - #70

Merged
Wattenberger merged 2 commits into
mainfrom
aw/cleanup
Dec 6, 2022
Merged

Clean up block config#70
Wattenberger merged 2 commits into
mainfrom
aw/cleanup

Conversation

@Wattenberger

Copy link
Copy Markdown
Contributor

Just a little bit of cleanup:

  • removed hacky demos
  • removed block from block names
  • removed block from block ids (other than code & markdown blocks, to prevent breakage)
  • made the descriptions more consistent
  • remove vestigial sandbox config params

@jaked jaked left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment thread blocks.config.json
"title": "Drawing block",
"description": "A whiteboard tool",
"sandbox": false,
"id": "excalidraw",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe we should leave the ids alone? they don't matter much in the UI, and there is metadata that references them that would need updating.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we're okay for these really specific use cases - Blocks will default to the next most specific block if it can't find the one specified, so things like https://blocks.githubnext.com/githubnext/blocks/blob/main/examples/drawing.excalidraw?blockKey=githubnext__blocks-examples__excalidraw2&fileRef= will still work. More than gappy to revert if you feel strongly, though!

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

er, happy, not gappy

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do not feel strongly, garry on

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants