🔥 🔥 🔥 Open Source JIRA, Linear and Height Alternative. Plane helps you track your issues, epics, and product roadmaps in the simplest way possible.
Go to file
M. Palanikannan 0b1efb173f [refactor] Editor code refactoring (#3194)
* removed relative imports from editor core

* Update issue widget file paths and imports to use kebab case instead of camel case, to align with coding conventions and improve consistency.

* Update Tiptap core and extensions versions to 2.1.13 and Tiptap React version to 2.1.13. Update Tiptap table imports to use the new location in package @tiptap/pm/tables. Update AlertLabel component to use the new type definition for LucideIcon.

* updated lock file

* removed default exports from editor/core

* fixed injecting css into the core package itself

* seperated css code to have single source of origin wrt to the package

* removed default imports from document editor

* all instances using index as key while mapping fixed

* Update Lite Text Editor package.json to remove @plane/editor-types as a dependency.

Update Lite Text Editor index.ts to update the import of IMentionSuggestion and IMentionHighlight from @plane/editor-types to @plane/editor-core.

Update Lite Text Editor ui/index.tsx to update the import of UploadImage, DeleteImage, IMentionSuggestion, and RestoreImage from @plane/editor-types to @plane/editor-core.

Update Lite Text Editor ui/menus/fixed-menu/index.tsx to update the import of UploadImage from @plane/editor-types to @plane/editor-core.

Update turbo.json to remove @plane/editor-types#build as a dependency for @plane/lite-text-editor#build, @plane/rich-text-editor#build, and @plane/document-editor#build.

* Remove deprecated import and adjust tippy.js usage in the slash-commands.tsx file of the editor extensions package.

* Update dependencies in `rich-text-editor/package.json`, remove `@plane/editor-types` and add `@plane/editor-core` in `rich-text-editor/src/index.ts`, and update imports in `rich-text-editor/src/ui/extensions/index.tsx` and `rich-text-editor/src/ui/index.tsx` to use `@plane/editor-core` instead of `@plane/editor-types`.

* Update package.json dependencies and add new types for image deletion, upload, restore, mention highlight, mention suggestion, and slash command item.

* Update import statements in various files to use the new package "@plane/editor-core" instead of "@plane/editor-types".

* fixed document editor to follow conventions

* Refactor imports in the Rich Text Editor package to use relative paths instead of absolute paths.

- Updated imports in `index.ts`, `ui/index.tsx`, and `ui/menus/bubble-menu/index.tsx` to use relative paths.
- Updated `tsconfig.json` to include the `baseUrl` compiler option and adjust the `include` and `exclude` paths.

* Refactor Lite Text Editor code to use relative import paths instead of absolute import paths.

* Added LucideIconType to the exports in index.ts for use in other files.
Created a new file lucide-icon.ts which contains the type LucideIconType.
Updated the icon type in HeadingOneItem in menu-items/index.tsx to use LucideIconType.
Updated the Icon type in AlertLabel in alert-label.tsx to use LucideIconType.
Updated the Icon type in VerticalDropdownItemProps in vertical-dropdown-menu.tsx to use LucideIconType.
Updated the Icon type in BubbleMenuItem in fixed-menu/index.tsx to use LucideIconType.
Deleted the file tooltip.tsx since it is no longer used.
Updated the Icon type in BubbleMenuItem in bubble-menu/index.tsx to use LucideIconType.

* ♻️ refactor: simplify rendering logic in slash-commands.tsx

The rendering logic in the file "slash-commands.tsx" has been simplified. Previously, the code used inline positioning for the popup, but it has now been removed. Instead of appending the popup to the document body, it is now appended to the element with the ID "tiptap-container". The "flip" option has also been removed. These changes have improved the readability and maintainability of the code.

* fixed build errors caused due to core's internal imports

* regression: fixed pages not saving issue and not duplicating with proper content issue

* build: Update @tiptap dependencies

Updated the @tiptap dependencies in the package.json files of `document-editor`, `extensions`, and `rich-text-editor` packages to version 2.1.13.

* 🚑 fix: Correct appendTo selector in slash-commands.tsx

Update the `appendTo` function call in `slash-commands.tsx` to use the correct selector `#editor-container` instead of `#tiptap-container`. This ensures that the component is appended to the appropriate container in the editor extension.

Note: The commit message assumes that the change is a fix for an issue or error. If it's not a fix, please provide more context so that an appropriate commit type can be determined.
2023-12-22 18:10:18 +05:30
.github fix: branch build fix (#3214) 2023-12-22 18:08:36 +05:30
apiserver fix - file size limit not work on plane.settings.production (#3160) 2023-12-22 18:09:39 +05:30
deploy fix: typo in install.sh (#3136) 2023-12-18 12:17:15 +05:30
nginx fix: environment file missing for space (#3105) 2023-12-14 16:18:02 +05:30
packages [refactor] Editor code refactoring (#3194) 2023-12-22 18:10:18 +05:30
space [refactor] Editor code refactoring (#3194) 2023-12-22 18:10:18 +05:30
web [refactor] Editor code refactoring (#3194) 2023-12-22 18:10:18 +05:30
.deepsource.toml chore: optimizations and file name changes (#2845) 2023-12-07 19:59:35 +05:30
.dockerignore fix: adding sentry configs on space app and updated docker ignore (#3018) 2023-12-07 19:59:35 +05:30
.env.example feat: Instance Registration and Configuration (#2793) 2023-12-07 19:59:35 +05:30
.eslintrc.js New Directory Setup (#2065) 2023-09-03 18:50:30 +05:30
.gitignore dev: Self Hosting with private repo fixes (#2787) 2023-12-07 19:59:35 +05:30
app.json chore: update single click deployments (#1141) 2023-05-26 14:04:15 +05:30
CODE_OF_CONDUCT.md chore: updated the contact email (#2605) 2023-11-02 16:27:23 +05:30
CONTRIBUTING.md fix: environment file missing for space (#3105) 2023-12-14 16:18:02 +05:30
docker-compose-local.yml fix: environment file missing for space (#3105) 2023-12-14 16:18:02 +05:30
docker-compose.yml dev: update bucket script to make the bucket public (#2767) 2023-12-07 19:59:35 +05:30
Dockerfile dev: remove unused packages (#3009) 2023-12-07 19:59:35 +05:30
ENV_SETUP.md chore: configurations (#3059) 2023-12-11 14:32:28 +05:30
heroku.yml chore: update single click deployments (#1141) 2023-05-26 14:04:15 +05:30
LICENSE.txt LICENSE change for Plane 2023-06-19 18:47:39 +05:30
package.json chore: format all files in monorepo (#3054) 2023-12-10 15:48:10 +05:30
README.md Fix: update self-host docs link in README (#3109) 2023-12-13 23:11:48 +05:30
setup.sh fix: environment file missing for space (#3105) 2023-12-14 16:18:02 +05:30
start.sh [chore] Update setup.sh, with removed replacement script & added project-level ENVs (#2115) 2023-09-13 20:21:02 +05:30
turbo.json [refactor] Editor code refactoring (#3194) 2023-12-22 18:10:18 +05:30
yarn.lock [refactor] Editor code refactoring (#3194) 2023-12-22 18:10:18 +05:30



Plane Logo

Plane

Flexible, extensible open-source project management

Discord online members Commit activity per month

Plane Screens Plane Screens

Meet Plane. An open-source software development tool to manage issues, sprints, and product roadmaps with peace of mind 🧘‍♀️.

Plane is still in its early days, not everything will be perfect yet, and hiccups may happen. Please let us know of any suggestions, ideas, or bugs that you encounter on our Discord or GitHub issues, and we will use your feedback to improve on our upcoming releases.

The easiest way to get started with Plane is by creating a Plane Cloud account. Plane Cloud offers a hosted solution for Plane. If you prefer to self-host Plane, please refer to our deployment documentation.

Contributors Quick Start

Prerequisite

Development system must have docker engine installed and running.

Steps

Setting up local environment is extremely easy and straight forward. Follow the below step and you will be ready to contribute

  1. Clone the code locally using git clone https://github.com/makeplane/plane.git
  2. Switch to the code folder cd plane
  3. Create your feature or fix branch you plan to work on using git checkout -b <feature-branch-name>
  4. Open terminal and run ./setup.sh
  5. Open the code on VSCode or similar equivalent IDE
  6. Review the .env files available in various folders. Visit Environment Setup to know about various environment variables used in system
  7. Run the docker command to initiate various services docker compose -f docker-compose-local.yml up -d

You are ready to make changes to the code. Do not forget to refresh the browser (in case id does not auto-reload)

Thats it!

🍙 Self Hosting

For self hosting environment setup, visit the Self Hosting documentation page

🚀 Features

  • Issue Planning and Tracking: Quickly create issues and add details using a powerful rich text editor that supports file uploads. Add sub-properties and references to issues for better organization and tracking.
  • Issue Attachments: Collaborate effectively by attaching files to issues, making it easy for your team to find and share important project-related documents.
  • Layouts: Customize your project view with your preferred layout - choose from List, Kanban, or Calendar to visualize your project in a way that makes sense to you.
  • Cycles: Plan sprints with Cycles to keep your team on track and productive. Gain insights into your project's progress with burn-down charts and other useful features.
  • Modules: Break down your large projects into smaller, more manageable modules. Assign modules between teams to easily track and plan your project's progress.
  • Views: Create custom filters to display only the issues that matter to you. Save and share your filters in just a few clicks.
  • Pages: Plane pages function as an AI-powered notepad, allowing you to easily document issues, cycle plans, and module details, and then synchronize them with your issues.
  • Command K: Enjoy a better user experience with the new Command + K menu. Easily manage and navigate through your projects from one convenient location.
  • GitHub Sync: Streamline your planning process by syncing your GitHub issues with Plane. Keep all your issues in one place for better tracking and collaboration.

📸 Screenshots

Plane Views

Plane Issue Details

Plane Cycles and Modules

Plane Analytics

Plane Pages

Plane Command Menu

📚Documentation

For full documentation, visit docs.plane.so

To see how to Contribute, visit here.

❤️ Community

The Plane community can be found on GitHub Discussions, where you can ask questions, voice ideas, and share your projects.

To chat with other community members you can join the Plane Discord.

Our Code of Conduct applies to all Plane community channels.

⛓️ Security

If you believe you have found a security vulnerability in Plane, we encourage you to responsibly disclose this and not open a public issue. We will investigate all legitimate reports. Email engineering@plane.so to disclose any security vulnerabilities.