jfallaire / generator-ps-boilerplate-project Goto Github PK

• Need to add a mention regarding Shares Drives option in Docker for Windows.
• Update step:build instructions (need to remove &&) into following command :

docker-compose down &&
docker-compose build && 
docker-compose up -d --remove-orphan

when running webpack dev server inside of a docker container on windows machine, the changes to the source files are not picked up by webpack

There are multiple vulnerabilities (lodash, semantic release, ...).

Add support to Inform users the generator requires to be updated in a non-intrusive way.
update-notifier npm package seems to be a good candidate for it :)

In this file: https://github.com/jfallaire/generator-ps-boilerplate-project/blob/develop/generators/simple/templates/views/utilities/globalHeader.ejs

Nice to have feature: Add option to toggle between light theme and dark theme

We should append the "project/client" name to the library name defined in webpack.common.config.js to avoid conflicts with other potentials Coveo JS UI custom extensions.

We have to change the copyright notice in the page footer.
At least, it shouldn't be jfallaire hardcoded.

see generators/iow/templates/conf.py lines 56-57

After following instructions on how to Authorize an Org Using the JWT-Based Flow in readme when sfdx force:auth:jwt:grant command is executed we are getting the following error :

ERROR: This org appears to have a problem with its OAuth configuration. Reason: invalid_grant - audience is invalid

adding this environment variable fix the issue:

export SFDX_AUDIENCE_URL=https://test.salesforce.com

Reference : https://salesforce.stackexchange.com/questions/252008/this-org-appears-to-have-a-problem-with-its-oauth-configuration-reason-invalid

When running this command : "docker-compose -f docker-compose.builder.yml run --rm install"
I faced this error :
error while creating mount source path '/host_mnt/d/Code/ps_***': mkdir /host_mnt/d: file exists, reset "shared drives" credentials)
This is caused when your credentials are wrong in docker (you changed them since generating docker or they have expired.)
To fix this, simply reset your credentials in the following window :

I'd add this in the README file.

Since Servicenow is fetching the search page directly from the Coveo platform, we should add a flow to compile and deploy the code (html, JS, CSS) to the appropriate hosted search page.

There is a problem with the npm run build.
In file webpack.prod.config.js, the generated config of vfComponents is empty for the third line, when generating all salesforce components :

Changing this line make the build work.