How sarapalac10/proyecto-final-bootcamp-fiori works
Main Components
• Frontend/UI Layer:
• Represented by the “webapp” folder which contains all UI-related files.
• Important files include Component.js (initialization logic), manifest.json (app configuration), index.html (startup page), and various XML views (App.view.xml, Home.view.xml, Detail.view.xml) and fragments.
• Controllers:
• The “webapp/controller” directory holds controllers (App.controller.js, Home.controller.js, Detail.controller.js) that control UI behavior.
• Models and Data Binding:
• “webapp/model” includes model definitions and formatters to bind data to the views.
• Services & Data Layer:
• “webapp/localService” (with its contained metadata.xml file) indicates the use of local service configurations, while the README specifies the use of an external OData service (https://services.odata.org/northwind/northwind.svc/).
• Testing:
• The “webapp/test” directory includes integration (OPA tests) and unit tests which ensure application quality.
• Utility Files:
• “webapp/utils” contains helper classes (e.g., HomeHelper.js and HomeService.js) to support business logic and service interactions.
Relationships and Interactions
• The UI layer (views and fragments) is rendered based on the structure defined in the Component.js and configuration in manifest.json.
• Controllers manage the interaction between the views and the data models.
• The models connect to the data sources (OData service and local service defined in localService/mainService) to supply data to the views.
• Test components interact with the core modules and validate the data flow and UI behaviors.
Architectural Patterns
• MVC Architecture: Clearly differentiate between models (data binding and service connectivity), views (XML layouts and UI fragments), and controllers (business and UI flow logic).
• Layered Approach: Highlight the separation between presentation (UI5 view and controller layers) and business/data (models and OData integration).
Technologies and Tools
• SAPUI5 Library and UI5 Tooling: The project uses UI5 versions (e.g., version 1.134.1) as defined in the README.
• OData Services: Representing how data is obtained from the SAP backend (using the sample Northwind service).
• Tooling Integration: Note the use of NodeJS (with package.json and package-lock.json) for building and running the app.
• Testing Frameworks: Indicate the integration of QUnit-based unit tests and OPA integration tests.
Elements
• Clearly labeled components:
• “Component.js / App Initialization”
• “Views & Fragments” (grouping all XML views and fragments)
• “Controllers” (listing App, Home, and Detail controllers)
• “Models & Data Binding” (including formatter and models scripts)
• “Local Service” (localService/mainService with metadata)
• “OData Service (Northwind)” as an external service.
• From the Component initialization to controllers.
• From controllers to views (to represent data binding and control logic).
• From models to both controllers and views.
• Testing modules (delineated separately to illustrate test coverage).