Angular development in 8.2

Spent a couple of days working on figuring out development on the Angular portal in 8.2. My findings so far:

- VS code 1IM extension:
   - Sort of works, for initial setup and compilation
   - For every start of VS code, you have to define the development folder. This overwrites all existing files, so it makes the extension completely unusable.
   - Setting the "API client" gives an error, I've no idea what this does.
   - Summa summarum, not usable at all at this point. Any development must be done with the command line imxclient

- Building
   - Several tarballs missing from imx-modules, these can be found in the installation media under addons (why are these not bundled in the project?)
   - All imx libs must be explicitly added with ng add to npm packages
   - Several build files missing, some projects do not build oob. I was able to create these manually.
   - There are several projects missing completely from the sources
   - Dev server does not start because of the missing projects (like DPR)
   - I did manage to build the required modules (ATT, QBM, QER, TSB) and managed to build the actual portal project

- Branches, publishing
   - No idea what is the purpose of branches? I can create a branch and compile it, also select it and compile in the API designer, but no idea how to "view" a branch with browser.
   - No tools to merge branches, no apparent change management i.e. how to transport changes or how to manage chg labels with these.
   - How are changes published to IIS? No matter how much I build, full compile DB and reset IIS, I see no changes. Is there a publish button somewhere? Can't see changes either when running "run-apiserver" from imxclient.

Any info on how to actually publish the portal project would be nice.

Parents
  • I completely agree with your assessment – development in Angular on 8.2 seems like quite the uphill battle. The lack of proper tools and documentation around branches, missing build files, and unclear publishing workflows is definitely frustrating. It sounds like the process requires a lot of manual fixes and guesswork, which shouldn’t be the case for such a system. Your point about missing tools for branch management is particularly valid – it’s hard to work efficiently without clear guidance on merging or publishing. For projects like this, leveraging expertise in modern technologies is crucial. Companies like The Frontend Company specialise in frameworks like Angular, React, and Vue.js, and they can provide valuable insights or solutions. For more details, have a look at their saas design services.

Reply
  • I completely agree with your assessment – development in Angular on 8.2 seems like quite the uphill battle. The lack of proper tools and documentation around branches, missing build files, and unclear publishing workflows is definitely frustrating. It sounds like the process requires a lot of manual fixes and guesswork, which shouldn’t be the case for such a system. Your point about missing tools for branch management is particularly valid – it’s hard to work efficiently without clear guidance on merging or publishing. For projects like this, leveraging expertise in modern technologies is crucial. Companies like The Frontend Company specialise in frameworks like Angular, React, and Vue.js, and they can provide valuable insights or solutions. For more details, have a look at their saas design services.

Children
No Data