Challenge Overview
Welcome to the Hestia CC | Table and Add/Edit Enhancements Challenge. In this challenge, we are looking for you to update the existing functionalities based on the requirements listed in this spec.
Let us know any question you have!
Technology stack
- NodeJS
- Angular 7
- JavaScript
Optional (As APIs are hosted)
- Java 11 (OpenJDK)
- Springboot
- REST
- Microsoft Azure
- MS-SQL
General requirements
Code Quality
- Important!! 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 and 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
- To fetch data from the API create different services. Do NOT use single service for data handling.
- 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.
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.
Layout
- Minimum supported resolution is 1366x768 px. The UI application is fluid, it expands automatically beyond 1366px width.
- Make sure you test the integrated code with chrome browser since the Web UI is supposed to be desktop responsive.
Platform
- Desktop: Chrome Browsers (Mac & Windows).
- All other browsers are out of scope. This is an internal application and the client will only be using Chrome.
Application requirements
0 Resource & links
- The existing application can be found in the forum.
- NEW API URL: Refer to the challenge forum.
- Marvel-app storyboard: https://marvelapp.com/888978d/screen/54568722.
1. Update the default view of the table details page.
- By default on the table detail pages: https://hestiafrontend.azurewebsites.net/details/user_schema1/HotDeals the table should show the business owned columns only. After this, a user should be able to show/hide tables using Column Settings sections.
- If a user refreshes the page then the table should retain the column show/hide state.
- Ref: new response: https://d.pr/free/i/g2WYNo .
- A column having flag business: false considered as a non-business column, all other columns are business columns.
2. Update sorting the tables on Dashboard
All tables on the Dashboard page should sort the data such that recently edited records at placed on top. For implementing this sort the table based on modified date & show the most recent records on top.
3. Add records page & Edit records page should contain all business columns.
- The Add records page & edit records page should allow adding/editing of the contents of all business columns.
- A new record can be added or edited from the table details page similar to this: https://hestiafrontend.azurewebsites.net/details/user_schema1/HotDeals
- Ref: new response: https://d.pr/free/i/g2WYNo .
- A column having flag business: false considered as a non-business column, all other columns are business columns.
4. Fix table heading name
- Ref: https://d.pr/free/i/2WHUZg
- If the column name is in the upper case then it is displayed as spaced sperate letter.
- Update code in top-toolbar.component.html:172 such that heading like PRODUCT_GROUP_NK should be displayed as 'Product Group Nk' column heading like endedByAssociate should be displayed as Ended By Associate
Final Submission Guidelines
- Full source code with all the requirements implemented.
- Detailed readme in markdown format that describes how to configure, build and run the app.
- Verification video or doc.
Licenses & attribution
- Third-party assets used to build your item must be properly licensed or free for commercial use. MIT, some modified BSD, Apache 2 licenses are ok. If a library is not commercial friendly you will need to get our approval first.
- Sufficient information regarding third-party assets must be present in your documentation. This includes the author, license info and a direct link to the asset online.
FAQs
After submission as a submitter what should be my next step?
Once the challenge submission phase is over the assigned reviewers are going to review all the submissions based on the challenge scorecard. They are expected to raise all issues found in the submissions they are reviewing. After the completion of review phase the Appeal phase status. In this phase, the submitters should go to the Online Review page, select the project & have a look at the issues raised by the reviewers. If you disagree with the reviewer on any issue/comment, raise an appeal by clicking the 'Appeal' button associated with the section and entering the appeal comment.
When & where I can see the challenge results?
After the Appeal response phase is over the results are displayed on the challenge specification page as well as on the online reivew page.