- Add base date time component with common methods
- Add Components
- Register components in dynamic components manifest
- Add sample usage to list view
- Add karma/jasmine tests
- Update SystemConfigHander
-- Add ability to map config name
-- Add ability to map config value
-- Add SystemConfigMappers.php to store config mappers
- Update UserPreferenceHandler
-- Add ability to map preference name
-- Add ability to map preference value
-- Add UserPreferencesMappers to store preferences mappers
- Configure config mappers for date format
- Configure preference mappers for time format
- Update unit tests
- Add UnitTester to hook into codeception login when executing tests.
- Create _beforeSuite and _before methods to reduce code duplication and improve performance.
- Add static closures where possible for better scoping and performance.
- Fix missing typehints/PHPDocs.
Signed-off-by: Dillon-Brown <dillon.brown@salesagility.com>
- Add base field class
- Add base number class
- Add int field detail mode component
- Add float field detail mode component
-- Format using user preferences or system config
-- Add NumberFormatPipe to format using preferences
- Add fields to manifest
- Add sample to list view
- Add jasmine tests
- Update button component
-- Update model to support passing a click handler
-- Update html
-- Add unit tests
- Add ModuleNavigation Service
-- Groups module and module action navigation actions
-- Change Navbar and other components to use this service
- Update action menu
-- Retrieve menu action information
-- Retrieve labels
-- Render buttons
- Change List and ListHeader components to grab data and pass it down
- Update ModuleTitle component to title as input and display it
- Update and add jasmine test for these components
- Import language languageFacade into logout component
- Add logout-link-model.ts
- Add logout-model.ts
- Update the logout component HTML to use an async pipe
Signed-off-by: Dillon-Brown <dillon.brown@salesagility.com>
- Add configurable exclusions by module / action on the backend
-- Add ClassicViewRoutingExclusionsHandler to grab these from legacy
-- Expose these as system configs to the frontend
- Update redirect check to classic view
-- Do not re-direct when same route (example, for listview filtering)
-- Do not re-direct when route is excluded
-- Do not re-direct when not able to convert route
- Update unit tests
- Replace hardcoded labels with translations
- Replace hardcoded html with dynamic list
- Add router links to related create views.
- Fix wrong usage of div instead of ul
- Add current module and action to AppState
- Calculate current module and action in BaseModuleResolver
-- Add logic to show current module as active on
--- import and find duplicates
- Update legacy handler method to retrieve available modules
-- Also send invisible modules, to
--- Allow to display invisible modules as the selected module
-- Update module name mape
- Retrieve number of navbar items from backed
- Fix grouped tab links
- Simplify navbar abstract by simplifying parameters
-- passing language map instead of individual language
-- passing navigation object instead of individual parts
- Create smaller components for repeated parts of navbar
-- grouped-menu-item
-- menu-item
-- menu-item-link
-- menu-item-list
-- home-menu-item
-- home-menu-recently-viewed
- Removing "jsdoc/no-types" from eslint
-- To avoid conflicts with jsdoc/require-param-type
- Implement UserChecker to check user deletion status on pre/post auth.
- Modify LoginFormAuthenticator to use Symfony/Security to fetch user data.
- Add Security Exceptions: UserDeletedException, UserNotFoundException.
- Set the security firewall to run the UserChecker.
- Update User Entity with deleted getter.
Signed-off-by: Dillon-Brown <dillon.brown@salesagility.com>
- Add login auth guard
-- Check if session is active on front end, if so go to home page
-- Check if session is active on backed, if so go to home page
-- Otherwise stay on login
- Add loaded flag to AppStateFacade to:
-- Know if the page has already been loaded
-- Avoid doing an extra request to the backed if we logged out on the frontend
- Enable angular router onSameUrlNavigation to:
-- Allow refreshing pages
-- Properly updating url when trying to go from home to login, which goes back to home
- Check session when moving between classic views
-- Update backend session-status entry point to also check legacy session
- Check if classic view iframe was re-directed to login page
- Logout user in the above
- Add conditional redirect to auth service logout
- Add key based loading to fix issues with loading on logout.
- Update jasmine tests
- Add button-loading directive to update button according to loading state
-- Add ability to listen to AppStateFacade loading state
-- Add ability to listen to loading input from parent component
- Add jasmine unit tests
- Fix action-name-mapper jasmine unit tests
- Add legacy handler to access RouteConverter
- Add legacy handler to access ModuleNameMapper
- Add legacy handler to access ActionNameMapper
- Remove action and module name maps from Suite8 side
- Update frontend route converter to check for suite 8 routes
-- When link is a suite 8 route does not convert
- Add LegacyScopeState to allow for nested legacy handler calls
-- Add abstract getHandlerKey to base LegacyHandler
-- Implement getHandlerKey on all legacy handlers
- Update legacy handler init and close methods to use scope state
-- Check if withing an already open legacy handler scope
- Move RouteConverter to legacy
- Move ModuleNameMapper to legacy
- Move ActionNameMapper to legacy
- Add smarty function to convert links
- Convert legacy links into Suite 8 links
-- Change mvc_utils::ajaxLink for most common links
-- Change ListViewGeneric links for list view links
-- Change DashletGenericDisplay for common dashlet links
- Listen to legacy non-view calls on the LegacyRedirectListener
- Add LegacyNonViewActionRedirectHandler to re-direct to legacy
-- Using 307 re-direction response to support post re-direction
- Add unit test for LegacyNonViewActionRedirectHandler
- Listen to legacy api calls on the LegacyRedirectListener
- Add LegacyApiRedirectHandler to re-direct to legacy endpoint
-- Using 307 re-direction response to support post re-direction
-- Using api_paths.yaml with the configuration with paths to check
- Setup API tests using codeception
-- Add helper methods to login in v4 and v8 API
- Add Api test to create account using v4 api
- Add Api test to create account using v8 api
- Add unit test for LegacyApiRedirectHandler
- Change Classic view component to use Iframe to render legacy view for specified url
- Add Iframe page change observer to detect page changes and route to appropriate view
-- Move legacy to suite8 route conversion to the front end
- Add Iframe resize observer to re-adjust the iframe size according to its contents
- Expose module and action name maps to the frontend within thee system configs
- Add unit and karma tests and ajdust existing ones
- Add floating to messages alert
- Make classic view resolver extend the base metadata resolver
- Move all front end calls to the default_module config to a single place
- Map default module name to frontend name in the legacy handler
- Add styling to display default logo and custom logo properly in desktop and responsive layouts
- Fix responsive layout for language
-- Adjust html
-- Adjust select css for login component
- Fix responsive layout for footer
- Add ability to fully start legacy app on legacy handlers
- Update Navbar and UserPreferences handler to start the legacy app after init
- Update Navbar and UserPreferences handler to implement the corresponding interfaces
-- Update corresponding Data providers to use the new interfaces
- Change Navbar legacy handler to take into account the tab configured preferences
-- based on the implementation used in Legacy SugarView
- Update UserPreferences to use the currently logged in user
-- remove hard coded user
-- get UserPreferences from the legacy User object instead of grabbing it directly from the db
- Add All entry to grouped tabs
- Adjust unit tests
- Catch missing exception
- Add extra exception handling on the backend and send error back to front end.
- Handler errors on the front-end and show message.
