Closed hn3000 closed 4 months ago
Hi @hn3000, thanks for reporting this issue! I'm also seeing this same behavior. @millerds can you please help with this issue? Thanks!
This is a problem with the CF templates not generator-office . . . transfering there.
I think the master branch needs to be pushed to the yo-office branch to get some needed changes (including a library version updated).
This is a problem with the CF templates not generator-office . . . transfering there.
I think the master branch needs to be pushed to the yo-office branch to get some needed changes (including a library version updated).
@millerds Is there any reason I shouldn't do this right now?
When I tried to validate the changes in the master branch a few weeks ago (using the --prerelease flag) the project didn't work. I didn't have time to investigate then and don't recall the error now. There is no reason not to do this now assuming the current set of changes don't have a different problem.
@millerds Updating the yo-office branch did not fix it. This does not reproduce locally. When I run
node convertToSingleHost.js xml zzz
I get the proper manifest with "zzz" as the DisplayName and a random GUID as the ID.
I ran:
node convertToSingleHost.js xml undefined zzz
I got exactly the symptoms of this Issue: "zzz' is in ID and "undefined" is in DisplayName.
So, I think something is wrong in the way the generator is reading the user's responses and and/or how it constructs the arguments to pass to the conversion script.
Would be OK with you to move this issue to the generator repo?
I get it now. The problem is that generator-office calls a standard convert script call with the same arguments . . . but when we updated this convert script we took out the "host" argument because it seemed unnecessary. I think the right change is to the convert script to take the host argument and remain uniform with the other template repos instead of doing the one off deal.
Since it was broken with my merge I can take responsibility for fixing it here.
This should be fixed now.
Prerequisites
Please answer the following questions before submitting an issue.
Expected behavior
Following the tutorial, I expected
yo office
to generate a valid Office Add-in, butnpm run start:desktop
opened a window without the new add-in loaded (and no visible error messages).Current behavior
The generated manifest has the project name as it's ID (which
npm run validate
flags as invalid). I expected to either get a fully valid manifest to be generated or the tutorial to mention the additional step. Part of the original problem was probably OfficeDev/generator-office#820 (although I didn't see an error message).Steps to Reproduce
Please provide detailed steps for reproducing the issue.
npx yo office
<Id>zzz</Id>
I followed the tutorial at https://learn.microsoft.com/en-us/office/dev/add-ins/quickstarts/excel-quickstart-jquery?tabs=yeomangenerator .
Context
Failure Logs
Please include any relevant log snippets, screenshots or code samples here.