GnG EPC integration | Edit

Welcome to the GnG EPC Integration | Edit Challenge. In this challenge, we are looking for you to integrate the backend API with the existing Angular 2+ Application.

Technology Stack

• NodeJS
• Angular 7
• JavaScript
• REST

General Requirements

Data Loading & Alerts

• Use loading animation effect to show the progress when loading data.
• Sanck-bar/toast should be used to show the error, success & warning messages when data is loaded from API. It shouldn't be shown for every successful API call, use your best judgment to show these.

Code Quality

• Reuse the existing code, components, CSS, js, etc as much as possible instead of duplicating the code.

Code formatting

• Make sure code is well documented, all classes, methods, variables, parameters, return values must be documented in every single code file, and appropriate inline comments should be provided too where the code is not straightforward to understand.
• Please use clean INDENTATION for all HTML code so future developers can follow the code.
• Use appropriate linter to validate your code.

Framework specific

• Use Observable & Observable.subscribe() method wherever applicable. You may refer this: https://angular.io/tutorial/toh-pt4#subscribe-in-heroescomponent
• Use Dependency Injection coding pattern.
• ng build should work without throwing any error.
• All type of responses 200, 401, 403 & 404 should be handled.

HTML Specific

• HTML should be valid HTML5 compliant.
• All HTML code naming should not have any conflicts or errors.
• Element and Attribute names should be in lowercase and use a '-' or camel naming to separate multiple-word classes (i.e.. 'main-content', or 'mainContent)
• Use semantically correct tags- use H tags for headers, etc. Use strong and em tags instead of bold and italic tags.
• No inline CSS styles- all styles must be placed in an external stylesheet.

CSS Specific

• Use CSS3 Media Queries to load different styles for each page. Do not build a different page for different device/layout.
• You may use SCSS in the project.

Platform

• Desktop: Chrome latest, Firefox latest (Mac & Windows), Safari latest (Mac), IE11+ (Windows), MS Edge

App Requirement

0 Resources & links

• API mappings, API details, base submission & storyboard details are provided in the challenge forum.
• Base branch is dev
• Storyboard
• Most of the code of EPC module is kept inside app/electric folder. While integrating APIs keep all your code/updates in this folder. Avoid doing changes in other folders unless it's required.

1 Sidebar & Header

1. These sections are already been developed. No change is required here.

2 Landing page

• ref: https://marvelapp.com/1fj39i6g/screen/58733920
• Clicking the New Sample button after entering sample name in the text-box should navigate to the Add sample page, with the name of the sample same as that was entered before.
• Clicking the New Sample button with the sample name empty should highlight the textbox border with red color to represent the error state. After this, when the user focuses this text-box then clear the error state.

4 Edit Sample page

• ref: https://marvelapp.com/1fj39i6g/screen/58733924
• On clicking the Save button, the created a new sample by sending PUT services/brp/data/{id} request to the API server. Ref to the mapping doc attached in the forum for more details.
• Clicking the Cancel link should navigate back to the details page without committing any changes. i.e https://marvelapp.com/1fj39i6g/screen/58733921

5 Upload XLS file

• ref: https://marvelapp.com/1fj39i6g/screen/58733924
• Upload XLS file should update the form data based on the uploaded file.
• It's up to you how you create & format the XLS file to import data on this form.
• Please include a sample XLS file in your submission.

6 Changes on details page

• Once the changes are made after editing the details page should show the Last changed values label & highlight the changes. Ref: https://marvelapp.com/1fj39i6g/screen/58733925