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

OSOE-92: Upgrade module to Node Extensions #59

Merged
merged 67 commits into from
Oct 31, 2022
Merged

OSOE-92: Upgrade module to Node Extensions #59

merged 67 commits into from
Oct 31, 2022

Conversation

sarahelsaig
Copy link
Member

Lombiq.VueJs/Manifest.cs Outdated Show resolved Hide resolved
Lombiq.VueJs/Lombiq.VueJs.csproj Outdated Show resolved Hide resolved
Lombiq.VueJs/.npmrc Show resolved Hide resolved
Lombiq.VueJs/Assets/Scripts/helpers/process-helpers.js Outdated Show resolved Hide resolved
Lombiq.VueJs/Lombiq.VueJs.targets Outdated Show resolved Hide resolved
Lombiq.VueJs/package.json Show resolved Hide resolved
Lombiq.VueJs/package.json Outdated Show resolved Hide resolved
Lombiq.VueJs/Assets/Scripts/helpers/rollup-pipeline.js Outdated Show resolved Hide resolved
Lombiq.VueJs/package.json Outdated Show resolved Hide resolved
Comment on lines 4 to 8
const args = process.argv.splice(2);
const argumentOptions = args.length >= 2 ? JSON.parse(args[1]) : undefined;

async function executeFunctionByCommandLineArgument(functions) {
if (!args[0]) return;
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm lost here.

  1. Is args populated when we call executeFunctionByCommandLineArgument directly, as we do in the compiler pipeline scripts?
  2. Does args contain anything else than functions itself?
  3. What is argumentOptions going to look like?

Please enlighten me!

Copy link
Member Author

Choose a reason for hiding this comment

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

  1. Args is the command line arguments from process.argv, basically runtime constants.
  2. It contains the name of the function, see here. Optionally it could contain a JSON that will expand the defaultOptions (e.g. custom root path, further rollup aliases). Configuring the options is not needed now, but iirc we needed it in Finitive (with GE) and may need it in the future.
  3. { "sfcRootPath": "Assets/Vue", "rollupAlias": { "batman": "../../../batman" } } (see traditional batman example)

Copy link
Member Author

Choose a reason for hiding this comment

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

I've refactored the function with more destructuring and explicit error messages to be cleaner and more developer-friendly.

@0liver 0liver merged commit ad3c72d into dev Oct 31, 2022
0liver pushed a commit that referenced this pull request Oct 31, 2022
This reverts commit ad3c72d, reversing
changes made to adeccab.
0liver pushed a commit that referenced this pull request Nov 25, 2022
0liver pushed a commit that referenced this pull request Nov 25, 2022
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