Added new issue type for working within a fork. This issue type reduces the overhead when working inside a fork. #1023
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Create simpleissue.yaml
Branch update
Related to #12 Add error handling for invalid `.roomodes` JSON syntax and display error message in RED on the "Prompts" page. * **CustomModesManager.ts** - Add `errorState` property to store error messages. - Update `loadModesFromFile` method to catch JSON syntax errors and set the error state. - Add `getErrorState`, `setErrorState`, and `clearErrorState` methods to manage the error state. * **CustomModesManager.test.ts** - Add tests to verify that an error message is displayed when there is an error in the `.roomodes` JSON syntax. - Update existing tests to handle the new error state logic. * **PromptsView.tsx** - Add `errorState` to component state. - Add logic to fetch the error state from `CustomModesManager` and update the component state. - Display the error message in RED beside the word "Modes" when there is an error in the `.roomodes` JSON syntax. --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/richardwhiteii/Roo-Code/issues/12?shareId=XXXX-XXXX-XXXX-XXXX).
updating from main.
Just adding more detail to this issues type. Based on the current ISSUE_TEMPLATE structure, it is difficult to just create an issue within a fork. This issue type allows for quickly capture an idea as an issue, without the overhead that is beneficial when contributing to the larger repo.
richardwhiteii
requested review from
ColemanRoo,
cte,
mrubens and
stea9499
as code owners
|
… PromptsView to eliminate unused error state
update from origin
from origin
[Fork] .roomodes json syntax
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Type of change
How Has This Been Tested?
I created tickets within my fork, and they worked.
Checklist:
Additional context
This is an issue template for contributors working in their fork.
Based on the current ISSUE_TEMPLATE structure, it is difficult to just create an issue within a fork.
This issue type allows for quickly capture an idea as an issue, without the overhead that is beneficial when contributing to the larger repo.
Related Issues
N/A
Reviewers
Important
Adds a new issue template
simpleissue.yamlfor creating simple issues within forks.simpleissue.yamlin.github/ISSUE_TEMPLATE/to create a simple issue template for forks.descriptionfield for describing the fork's purpose and planned changes.This description was created by
for a5c3039. It will automatically update as commits are pushed.