Coding in rIDE

StarterKit

rIDE is built on a powerful StarterKit template with an IDesign (Juval Lowry) inspired architecture. To learn more about the StarterKit and architecture, Skip to StarterKit.

Troubleshooting Common Issues

A collection of common coding issues is listed here: Skip to Troubleshooting. Or product team is actively working to address all these issues.

Code Editor

The vertical panels between the coding sections can be resized.

Our AI Code editor is trained on our StarterKit, IDesign Architecture pattern, and our tech stack (React, MUI, .NET/C#).

Spec Driven Development

We highly recommend using our Software Planning and Task Planning tools to implement a task. This helps make sure tasks are strategically implemented, can scale, and are of higher quality.

NOTE: We recommend encouraging the AI to do one task at a time and supervising the suggested changes so you have higher quality output.

Task Details

To open the current task details. Click the Open button in the top right. This will open up information about your task, requirements, and previous chat threads.

Restoring Previous Chat Threads

You can restore previous chat threads by clicking the Open button in the Task Details and selecting the previous chat threads.

Suggested Changes

The app will make suggested changes. You can approve, message RIDE to modify, or cancel these Suggested Changes.

NOTE: The suggested changes box has two scrolling containers. If you have a long code file you may have to scroll down to view all of the code and then place your mouse on the outside scroll bar to scroll down to be able to view the Accept Changes or Message buttons.

Focus Mode

Focus Mode helps you see only files that are relevant to the apps architecture.

Known Issue	Troubleshooting	Status
Focus Mode is missing: - Routes (react-app/src/routes_) - Front-End api folder (react-app/src/api) - .env (react-app) *git ignored - Appsettings.development.json (git ignored) - Program.cs (Services/App.Api)	Switch the toggle of focus mode and navigate to the file locations listed.	Not Reported.
Runtime Error: Failed to load resource: the server responded with a status of 404 (Not Found) :5123/app/invoke:1 Or Front-End Manager methods are not written as such. const CreateTaskAsync = (request: CreateTaskRequestDto): Promise => ApiClient.invokeMethod(“Api”, “TaskManager”,“CreateTaskAsync”, request);	The AI should not show these as suggested changes. Make sure the Manager Name is your manager name and the Service Name is “Api” Correct example: :5123/Api/invoke:1 Make changes to your manager to fix: const CreateTaskAsync = (request: CreateTaskRequestDto): Promise => ApiClient.invokeMethod(“Api”, “TaskManager”, “CreateTaskAsync”, request);	Not Reported.
‘AppConfiguration’ does not contain a definition for…	Copy and paste in error to chat box or add it to ask to add value to AppConfiguration. You will also need to add it to your appsettings.development.json file and the Environment in your Azure Static Web App (develop slot and production).	Not Reported.
System.InvalidOperationException: Service ‘MyManager’ not found	Need to add MyManager and any other Managers, Engines, or Accessors to the dependency injection in Program.cs. Don’t forget to re-run the back-end.	Not Reported.
CS0104: ‘X’ is an ambiguous reference between ‘Namespace1.X’ and ‘Namespace2.X’	The AI doesn’t take into consideration reserved keywords so avoid creating contracts with names like ‘task’. It will throw an ambiguous reference error. Rename the reserved keywords or have it specify a namespace.	Not Reported.