Known Issues

Known Issues from Project Audit

• Deployment to Test Environment is not working, because of errors in VPS instance's config - #142,
• Order of jobs in Test Environment's is random, jobs must be executed in predefined order - #142,
• "Deployments" section on GitHub repo's profile is not displaying any data,
• Real UI screenshot must be used instead of mockup,
• Make "Getting Started" section more distinctable between "getting started for developers" and "getting started for end users",
• "Table of Content" in ReadMe is missing link to "Contributions" section,
• "Environment" issue template not visible - #141,
• Migrate to newest Angular framework (standalone components)?
• Husky isn't always working, some commits are being created without additional formatting,
• No package version was setup on Web Frontend,
• Useless auto-generated Angular ReadMe in Web Frontend's folder,
• Try to use data mappings in TS where possible to remove additional interfaces on Web Frontend,
• All currently existing components of Web Frontend are residing in one page, Home, this must be refactored for future adaptability,
• Dialog components must be stored in shared directory, here Table Dialog component as example,
• There should be load indicators on frontend, to inform user, that something is being loaded,
• Web Frontend is not prepared for handling overflowing list of tables and tasks on display - #137,
• There are no predefined limits of data weight, like strings length, etc. - #137,
• No QA specification defined for Web Backend (code coverage, quality gates, etc.),
• No Integration tests provided for Web Backend,
• Enumerations must be stored as constants in Web Backend, here TaskShow as example,
• Missing authentication and authorisation mechanics - #88,
• Factories must be stored in dedicated folders on Web Backend, here GetProblemDetailsByExceptionFactory as example,
• Business Domain models must be separated from Persistence layer's logic,
• Exceptions constants must be stored in Application layer,
• "Configuration" folder is the same as "Extensions" folder in Persistence layer,
• Names of files on Web Backend must be more descriptive, here PersistenceServices as example,
• Program class must be more adaptable on Web Backend, to handle config data more robustly,
• Docker containers must be repaired and refactored to be able to run in Development and Production environments - #125,
• Wiki must provide info about adding/editing/deleting entities on Web Backend for preventing from omitting some mechanics (like create all models per layers, provide migrations, etc.),
• Wiki must provide info about UI elements (names of components maching mockups, UX/UI design guidelines, etc.),
• Wiki misses exact instructions how to handle Husky config and OpenAPI files regeneration procedures,
• Project Risks must include heavy requirements changes,
• Project Risks must include unexperienced developers dominance in dev team,
• Project Risks must include, that this project is being used as workflow creation environment for organisation,
• Project Risks must include, that this project can't be too complicated in terms of business domain and technology, as this project is intended to be training environment,
• Application should operate on entities based on GUIDs to better handle large amounts of data,
• Task completion must work on all tables while switching between each other,