Remove `run` (from Svelte/legacy Library) Calls From Project Creation Page

Introduction

As we continue to refine and improve our project creation page, it's essential to address the remaining legacy code that's still utilizing the run method from svelte/legacy. This tracking issue aims to remove these run calls and replace them with a more efficient and user-friendly approach. In this article, we'll delve into the details of this feature, its benefits, and the affected pages.

Describe the Feature

The project creation page is a crucial component of our platform, allowing users to create new projects with custom codes. However, the current implementation still relies on the run method from svelte/legacy, which was not converted in the previous update (#1652). This is due to the complexity of untangling the interaction between the run method and the lexSuperForm component.

To address this issue, we propose separating the concept of custom project code and auto-calculated project code into two distinct fields. This will enable users to submit both fields from the form, and the backend will determine whether to allow the custom project code or ignore it and use the calculated one. This approach will eliminate the infinite effect loops that occur when trying to convert run to $effect.

Benefits of the New Approach

The proposed solution offers several benefits, including:

• Improved User Experience: By separating custom project code and auto-calculated project code, users will have a clearer understanding of the project creation process and can make informed decisions about their project settings.
• Increased Efficiency: The new approach will eliminate the need for complex run method conversions, reducing the risk of infinite effect loops and making the project creation process more streamlined.
• Enhanced Security: By allowing the backend to determine whether to use custom project code or auto-calculated project code, we can ensure that project settings are validated and secure.

Who is this Feature for?

This feature is designed for users who can create projects with custom codes, including:

• Developers: Who will benefit from the improved user experience and increased efficiency of the project creation process.
• Admins: Who will appreciate the enhanced security and validation of project settings.
• Org Managers: Who will enjoy the streamlined project creation process and improved user experience.

Pages Affected

The project creation page will be the primary page affected by this feature. The changes will be implemented to ensure a seamless user experience and to eliminate the remaining legacy code.

Implementation Plan

To implement this feature, we will follow these steps:

1. Separate Custom Project Code and Auto-Calculated Project Code: We will create two distinct fields for custom project code and auto-calculated project code.
2. Submit Both Fields from the Form: Users will be able to submit both fields from the form, and the backend will determine whether to allow the custom project code or ignore it and use the calculated one.
3. Backend Validation: The backend will validate project settings and determine whether to use custom project code or auto-calculated project code.
4. Testing and Quality Assurance: We will thoroughly test the feature to ensure that it meets our quality standards provides a seamless user experience.

Conclusion

Removing run calls from the project creation page is a crucial step in refining our platform and providing a better user experience. By separating custom project code and auto-calculated project code, we can eliminate the remaining legacy code and ensure a more efficient and secure project creation process. We will continue to monitor and improve this feature to ensure that it meets the needs of our users.

Future Development

As we continue to develop and refine our platform, we will keep the following in mind:

• Legacy Code Removal: We will strive to remove all remaining legacy code and replace it with modern, efficient, and secure solutions.
• User Experience: We will prioritize user experience and ensure that all features and updates meet our quality standards.
• Security: We will continue to enhance security and validation of project settings to ensure a secure and reliable platform.

Q: What is the current issue with the project creation page?

A: The project creation page still uses the run method from svelte/legacy, which was not converted in the previous update (#1652). This is due to the complexity of untangling the interaction between the run method and the lexSuperForm component.

Q: Why is it necessary to remove the run calls?

A: Removing the run calls will eliminate the infinite effect loops that occur when trying to convert run to $effect. This will make the project creation process more streamlined and efficient.

Q: How will the new approach affect users?

A: The new approach will provide a clearer understanding of the project creation process and allow users to make informed decisions about their project settings. It will also eliminate the need for complex run method conversions, reducing the risk of infinite effect loops.

Q: Who will benefit from this feature?

A: This feature is designed for users who can create projects with custom codes, including:

• Developers: Who will benefit from the improved user experience and increased efficiency of the project creation process.
• Admins: Who will appreciate the enhanced security and validation of project settings.
• Org Managers: Who will enjoy the streamlined project creation process and improved user experience.

Q: What pages will be affected by this feature?

A: The project creation page will be the primary page affected by this feature. The changes will be implemented to ensure a seamless user experience and to eliminate the remaining legacy code.

Q: How will the backend determine whether to use custom project code or auto-calculated project code?

A: The backend will validate project settings and determine whether to use custom project code or auto-calculated project code based on the user's input.

Q: What is the implementation plan for this feature?

A: To implement this feature, we will follow these steps:

1. Separate Custom Project Code and Auto-Calculated Project Code: We will create two distinct fields for custom project code and auto-calculated project code.
2. Submit Both Fields from the Form: Users will be able to submit both fields from the form, and the backend will determine whether to allow the custom project code or ignore it and use the calculated one.
3. Backend Validation: The backend will validate project settings and determine whether to use custom project code or auto-calculated project code.
4. Testing and Quality Assurance: We will thoroughly test the feature to ensure that it meets our quality standards provides a seamless user experience.

Q: What is the timeline for implementing this feature?

A: We will implement this feature as soon as possible, with a focus on ensuring a seamless user experience and eliminating the remaining legacy code.

Q: How will this feature be tested and validated?

A: We will thoroughly test the feature to ensure that it meets our quality standards and provides a seamless user experience. This will include testing for security, performance, and functionality.

Q What is the next step after implementing this feature?

A: After implementing this feature, we will continue to monitor and improve it to ensure that it meets the needs of our users. We will also prioritize user experience, security, and legacy code removal in future development.