Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP on getting app-prop-viewer to load. Seems to get to component now… #3

Conversation

1000TurquoisePogs
Copy link

  • Fixed build problems. Environment object was missing
  • Add ng build to the package.json build instruction so you can npm run build because I never put npm tools in my global path and we dont tell people to either.
  • Remove "component factory" code of the angular-2-plugin-loader that was never used as far as I know (the "component.js" content)
  • Removed code about html2canvas. Dead code should not be kept around.
  • Update app-prop-viewer to newer versions of libraries
  • Update app-prop-viewer to webpack5 base config
  • Move externals requirejs loading from the externals.js file into the desktop.js file
    Before this, the app would try to do a GET on web/@angular/core/core.js
    After, it makes no request at all.
    Neither does desktop.js. The "externals" seem to work in the same way they always have, but now without the need for a separate "externals.js" and "externals-main.js"

NOTE: ng build removes require.js from the web folder. After building you still need to cp node_modules/requirejs/require.js web/...

@@ -56,7 +56,7 @@
"sourceMap": true
}
},
"defaultConfiguration": "production"
"defaultConfiguration": "development"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's this for?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

development, i need to see the source in the browser to debug.
it can be production when we're ready.

@@ -9,7 +9,7 @@
"scripts": {
"build:externals": "webpack --progress --config webpack.externals.js",
"start": "webpack --watch --progress",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can also update start script to be
"ng build --watch"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added

@DivergentEuropeans
Copy link

I am getting this, is this expected UI?

image

The console is very promising, some App Prop Viewer things are being loaded but not sure if I'm seeing what I'm supposed to

@DivergentEuropeans
Copy link

small addition: zowe#606

@1000TurquoisePogs
Copy link
Author

I am getting this, is this expected UI?

image

The console is very promising, some App Prop Viewer things are being loaded but not sure if I'm seeing what I'm supposed to

yes, but i dont know why it doesnt get further. perhaps some step is missing.

@wadkarsatish wadkarsatish force-pushed the v2.x/staging branch 2 times, most recently from 86ba78a to 6430bd8 Compare August 14, 2024 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants