pixiebrix/pixiebrix-extension

PixieBrix browser extension

pixiebrix-extension's Issues

Context menu template page

Add environment banner for dev/staging

Add Vue.js agent support

Drag and drop devtools support

Add utility CSS library for styling templates

Can use Tailwind CSS, but trim what what we don't need (e.g., media queries). Will also want to prefix with a pb- prefix to avoid collisions

• https://tailwindcss.com/
• https://github.com/salesforce-ux/postcss-slds-prefix

Devtools feature flagging

Extension point log in Workshop

• Errors with context, extension, brick, service, etc.
• Show which brick/service caused the error
• Filter by level
• Pagination

Panel template inference improvements

Devtools panel integration

Add OAuth2 support

Add Zapier support

Page editor UX improvements

Add XPath transformer support

Bump css-selector-generator

Improve marketplace UX

• List view instead of cards
• Searchable
• List services used
• Tags, e.g., sites covered, services used (e.g., Slack)
• Detail page w/ YAML

Upgrade to webpack 5

Plugin blockers:

• Extension loader plugin: rubenspgcavalcante/webpack-extension-reloader#110

Add ability to run an effect on a parent/target tabs

Enable an effect to run on the tab that opened it

Export headers for the built-in bricks and extension points

Export metadata for built-in bricks and extensions points so we can add placeholders in the registry

Google BigQuery support

Add testing infrastructure

• mocks/fakes for scripts calling into background page
• axios mocks

Add support for OpenAPI/Swagger

Support pulling in a OpenAPI/Swagger specification when making API calls

References:

• https://swagger.io/docs/specification/data-models/keywords/

Fix the GitHub build

Add UIPath orchestrator support

Marketplace activation wizard

• Select which extensions to activate
• Have users select configurations as part of installation
• Grant necessary permissions

Improve log stream

• show inputs to bricks
• show output from bricks

Refactor extension messaging protocol

Add eslint support

• pre-commit hook
• configuration

Add support for Firefox

References:

• https://github.com/mozilla/web-ext
• https://extensionworkshop.com/documentation/publish/submitting-an-add-on/

Firefox does not support extenally_connectable yet, so need a different way to exchange the token. Discussion:

• https://bugzilla.mozilla.org/show_bug.cgi?id=1319168
• https://discourse.mozilla.org/t/using-runtime-sendmessage-api-from-webpages/36984

Subtasks:

• Split webpack configs and add Firefox manifest
• Remove dependency on extenally_connectable
• Code splitting because Mozilla upload/signing only supports modules < 4mb. See #95

Move template engine and brick evaluation to Chrome sandbox

References/Documentation:

• Chrome: https://developer.chrome.com/extensions/manifest/sandbox
• Firefox: not supported by Firefox
  • https://discourse.mozilla.org/t/webextension-sandboxing-eval/13659
  • https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/user_scripts
  • https://bugzilla.mozilla.org/show_bug.cgi?id=1398662

Feature flags

Feature flags to help control rollout of beta features

Code splitting

Split code, necessary because Firefox has file size limits in extensions. Will also provide parsing performance benefit for startup

• icons
• widgets
• jq-web because it use web asm under the hood
• ace code editor

Also probably need to adjust the manifests to support loading the files

Prior Art:

• https://github.com/crimx/webpack-target-webextension
• https://github.com/jacksteamdev/rollup-plugin-bundle-imports#readme

Problems with Firefox

• https://bugzilla.mozilla.org/show_bug.cgi?id=1536094
• https://bugzilla.mozilla.org/show_bug.cgi?id=1451545

Write developer documentation

Write developer documentation for developers building/running locally

• Environment file
• Build commands
• https://v2.docusaurus.io/

Add support for text selection context menus

Add key to Chrome staging builds

https://developers.chrome.com/extensions/manifest/key

Brick selection UX

Brix selection search instead of the dropdown

• Name
• Id
• Description

Lodash overriding version on page

Breaks websites using older versions of lodash, e.g., Jira's active sprint page

• webpack/webpack#4465
• lodash/lodash#2671

Dynamic content script permissions

https://github.com/fregante/webext-dynamic-content-scripts

Add support for @local scope bricks

Add support for @local scope bricks that are saved/stored in local storage

Improve error messages for Google Sheets

• spreadsheet not found
• pixiebrix configuration error caused by the oauth client being set wrong

Add contextMenu editing support to Page Editor

Fix context menu lifecycle bugs

Add privacy-friendly usage analytics

Add semantic web/microdata reader

Automatically infer output schemas for readers

Ideally support incremental inference:

• https://www.npmjs.com/package/generate-schema
• https://www.npmjs.com/package/to-json-schema

Action to fill out a form

Automatically re-activate blueprint in brick editor

By default, automatically replace the user's currently installed blueprint with the new one they just saved when they are editing it in the brick editor

Devtools usability improvements

Support multiple menus on a page

• support multiple menus, e.g., for table rows, etc.
• each menu has its own reader context

Setup testing infrastructure

• Mocks
• GitHub CI

Support composite readers in the Page Editor