OfficeDev / OfficeDev/Office-Addin-Scripts
office-addin-manifest returns "The manifest is valid" through there isn't a matched resid in <Resources>
Open
Nobody has claimed this yet.
needs triage
- Dominant language
- TypeScript
- Stars
- 194
- Forks
- 117
- Avg merge
- 1d 32m
- Merged PRs (30d)
- 2
Description
Expected behavior
Verification fails with no matching resid
Current behavior
Return "The manifest is valid" through there isn't a matched resid in <Resources>
Steps to Reproduce
- Change any
residinside<ExtensionPoint>in an availablemanifest.xmlfile - Run
office-addin-manifest validate manifest.xml - you get it
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the office-addin-manifest validate command and reproduce the issue using a manifest.xml where an ExtensionPoint resid has been changed. Trace how validation checks Resources references; done means validation rejects the manifest instead of returning "The manifest is valid" when no matching resid exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100