MC-9766 - Reorganise the repo to support multiple Angular projects #435
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The source code for the
mdm-ui
application has been reorganised to support multiple Angular projects within the same workspace. This will prepare the repo to contain further UI applications/projects.Changes made:
src
folder have been moved toprojects/mdm-ui/src
. Files have been moved usinggit mv
command to only rename files and maintain original commit history.angular.json
file which is now responsible for all Angular projects inside this workspace.npm
scripts still work. The default workspace project is stillmdm-ui
, so existing commands likenpm start
will still default to servingmdm-ui
. Other scripts liketest
,eslint
,dist
etc have been updated to work with the new structure.Jenkinsfile
has been updated to ensure that any file references now point to new locations.@olliefreeman - I have asked for your review also specifically to check the
Jenkinsfile
. I've seen that a Jenkins branch build passes still, and becausenpm run dist
is used and still outputs the build output todist/mdm-ui-<version>,tgz
then there should not be any major changes with deployments.