Page Rendering Validation Logic Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing method of developing derivative business pages by adding rendering and validation logic to the initial business page results in bloated JavaScript, leading to debugging and maintenance challenges, and generates duplicate codes when each derivative business maintains its own page rendering and validation logic, increasing the workload for testing and error handling.
Innovation Solution
A method and device for rendering and validating pages by extracting general and derivative business configurations, encapsulating attribute and validation logic separately, and saving them in corresponding page configuration files, allowing for selective loading and binding based on user-selected business types, which reduces code duplication and improves maintenance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If rendering and validation logic are added to the initial business page to accommodate derivative businesses, then the page can support multiple business scenarios, but the JavaScript becomes bloated and debugging and maintenance become difficult
Solution Approach 1:
The patent segments the business logic by separating general business configuration from derivative business configuration. Each derivative business has its own configuration file that inherits from the general business configuration, allowing the system to support multiple business scenarios while keeping each business's logic isolated and manageable, thus preventing JavaScript bloat.
Solution Approach 2:
The patent creates a universal base configuration file that contains common business logic applicable to all derivative businesses. This general business configuration serves multiple functions across different derivative businesses, reducing code duplication and making the system more maintainable while supporting versatility.
2Adaptability or versatility
If each derivative business independently generates and maintains its own page rendering and validation logic, then each business can be customized, but duplicate codes are generated and testing workload increases
Solution Approach 1:
The patent merges common validation logic and rendering logic into shared configuration files that can be reused across multiple derivative businesses. By combining these common functionalities at the general business level, the system reduces code duplication while still allowing each derivative business to maintain its own customizations through inheritance.
3Adaptability or versatility
If common business configurations are modified, then the system can adapt to changing requirements, but multiple files need to be modified and errors may occur
Solution Approach 1:
The patent segments the configuration into a hierarchical structure where derivative business configurations inherit from a general business configuration. This segmentation allows modifications to be made at the appropriate level - common changes at the general level and specific changes at the derivative level - reducing the number of files that need to be modified and minimizing error risk.
Data Source
AI summary
The present invention provides a method and device for page rendering and validation. The method includes at least: extracting a general business configuration and a derivative business configuration based on similarities and differences between an initial business page and a derivative business page; encapsulating the general business configuration, and at the same time, separating respective attribute logic and validation logic from one or more derivative business configurations and then encapsulating them separately, in which the encapsulation of general business and the encapsulation of derivative business are respectively saved into corresponding page configuration files; according to a derivative business type selected by the user, the corresponding page configuration file being loaded to a page configuration file of general business, and a form validation method being bound to the page configuration file of general business.