Giter VIP home page Giter VIP logo

pnp / vscode-viva Goto Github PK

View Code? Open in Web Editor NEW
35.0 13.0 15.0 66.67 MB

With the SharePoint Framework Toolkit extension, you can create and manage your SharePoint Framework solutions on your tenant. All actions you need to perform during the development flow are at your fingertips.

Home Page: https://marketplace.visualstudio.com/items?itemName=m365pnp.viva-connections-toolkit

License: MIT License

JavaScript 1.44% TypeScript 91.93% CSS 0.86% PowerShell 5.77%
viva-connections viva m365 m365dev microsoft-teams sharepoint sharepoint-framework spfx

vscode-viva's Introduction

SharePoint Framework Toolkit for Visual Studio Code

SharePoint Framework Toolkit for Visual Studio Code

version installs

SharePoint Framework Toolkit is a Visual Studio Code extension that aims to boost your productivity in developing and managing SharePoint Framework solutions helping at every stage of your development flow, from setting up your development workspace to deploying a solution straight to your tenant without the need to leave VS Code. With SharePoint Framework, you can use modern web technologies and tools in your preferred development environment to build productive experiences and apps that are responsive and mobile-ready allowing you to create solutions to extend SharePoint, Microsoft Teams, Microsoft Viva Connections, Outlook and Microsoft365.com.

Capabilities | Architecture | Wiki | Contributing | Support | Code of Conduct | Changelog | Sharing is Caring | Additional resources

Sample Gallery

⭐ Capabilities

The extension provides the following capabilities:

1️⃣ Welcome experience

The extension automatically detects if you have a SharePoint Framework project opened. If not, it will start with a welcome experience that will guide you through the process of creating a new project and validating your local environment.

Welcome experience

Directly from this view, you may create a new project from scratch or from an existing web part, extension or ACE sample, or ACE scenario.

It is also possible to open an already existing project using Open folder button.

Last but not least it is possible to check your local workspace for the needed global dependencies to develop the SPFx solutions, like the correct Node version, gulp, yeoman etc., and install them if needed with a single click.

When running the extension for the first time it will present you a walkthrough that will give you a step-by-step guide to get started with SharePoint Framework development and will go over the main functionalities of SharePoint Framework (SPFx) Toolkit.

Walkthrough

Check out our docs for more details

2️⃣ Set up your development environment

To ensure that you can develop SPFx solutions, you may use the check dependencies functionality.

Validate dependency

This action will check if you have the required dependencies such as:

  • Node version: 18
  • NPM dependencies:
    • gulp
    • yo
    • @microsoft/generator-sharepoint

In case you do not have all dependencies installed, or some are incorrect version, you can use the install dependencies action to install them.

Note

The list of valid dependencies is based on set up your development environment recommendations

Check out our docs for more details

3️⃣ Don't Start from scratch. Reuse an SPFx (web part or extension) or ACE sample

You may kick-start your development with a new project based on an existing ACE or SPFx web part or extension with a click of a button. All of the provided samples are powered by PnP Samples repositories.

Sample gallery

The extension provides a set of filters to help you find the right sample for your needs. You may search by: author, title, description, SPFx version, and component type. It is also possible browse sample details view directly from VS Code checking all sample details before you create a new project.

Switch between the list and grid view and don't worry about the size of your VS Code as it is fully responsive.

Sample gallery is responsive

Check out how easy it is to create a new project based on a existing sample 👇.

Create project based on web part sample

Check out our docs for more details

4️⃣ Start from an ACE scenario

Start your solution based on the provided set of ACE scenarios with ready-to-use code to showcase what's possible. Scenarios are provided with detailed guidance using the Code Tour to provide you with more details on the structure and options.

5️⃣ Create a new project

Creating a new project was never easier. Just use the create a new project action, and the extension will guide you through the process with a dedicated scaffolding form.

Create new project

Check it out in action 👇.

Create new project

It's possible to scaffold any kind of SPFx project.

All SPFx project support

Install additional dependencies with a single click straight from the scaffolding form. Currently we support installing PnP reusable property pane controls, PnP reusable React controls, and PnPjs.

Additional dependency step

Check out our docs for more details

6️⃣ Login to your tenant & retrieve environment details

tenant info

The extension allows you to login to your Microsoft 365 tenant using CLI for Microsoft 365.

login

Thanks to that the extension will retrieve helpful URLs from your tenant like:

  • link to SharePoint main site
  • link to SharePoint admin site
  • link to SharePoint web API permission management page

Additionally, the extension will check and retrieve tenant service health incidents that are currently happening in your tenant so that you gain quick insights on your tenant health.

tenant details

After successful login an additional view is presented that shows list links to app catalogs available in the tenant, both tenant-level and all site-level app catalogs. Additionally it will show you all tenant-wide extensions installed on your tenant with.

tenant details

Login-in is also required for some actions to work properly like the deploy action which allows you to upload of the .sppkg file to the tenant or site-level App Catalog.

Additionally, when an SPFx project is opened the extension will check serve.json file and suggest updating it to set the properties based on the currently logged-in tenant.

validate serve

Check out our docs for more details

7️⃣ Gulp tasks

The extension shows all possible Gulp tasks one may run on an SPFx project. The tasks allow you to clean, bundle, package, serve the project with a single click.

Gulp Tasks

Check out our docs for more details

8️⃣ Actions

The actions section allows unique functionalities that may significantly boost productivity when working with SPFx projects.

Actions

Currently the extension allows you to:

  • CI/CD Workflow - This action will allow you to generate yaml CI/CD GitHub Workflow or Azure DevOps Pipeline to bundle, package, and deploy your project to any app catalog on every code push.

CI CD pipeline

Check it out in action for GitHub👇

GitHub CI CD workflow

And for Azure DevOps👇

Azure DevOps CI CD pipeline

Check out our docs for more details

  • Upgrade project - Uses CLI for Microsoft 365 to create a .md report with upgrade guidance to the latest supported SPFx version by the extension.

Upgrade project

Check out our docs for more details

  • Validate project - Creates a validation .md report against the currently used SPFx version in the project. The action will automatically detect the SPFx version used and will validate if the project is properly set up.

Upgrade project

Check out our docs for more details

  • Rename project - Forget about manual work and let the extension rename your project and generate a new solution ID.

Rename

Check out our docs for more details

  • Grant API permissions - The action will Grant all API permissions specified in the package-solution.json of the current project. This is especially helpful if you just want to debug your SPFx solution using Workbench. No longer do you need to bundle, package, and deploy the project to then go to the SharePoint admin portal and consent to the permissions. All of that is now done with just a single click.

Grant permissions

Check out our docs for more details

  • Deploy project - This action will only work when the user is logged in to tenant and the sppkg file is present. The action will deploy the project to the selected (tenant or site) app catalog.

Deploy

Check out our docs for more details

  • Add new component - Allows scaffolding a new SPFx project as a new component of the currently opened project. The action under the hood uses the same SharePoint Yeoman generator to scaffold a new project and this feature is an abstraction UI layer.

Add component

Check out our docs for more details

  • Open sample/scenario galleries of the SPFx web part, extensions, or ACEs projects - SharePoint Framework Toolkit supports a couple of sample galleries that may be used to scaffold a new SPFx project.

Check out our docs for more details

9️⃣ Help and feedback section

The help and feedback section is a group of links that will direct you to the right Microsoft documentation and learning paths. It also contains links to additional tooling that may be helpful in your development process as well as links to connect with the Microsoft 365 and Power Platform Community.

help and feedback

Check out our docs for more details

1️⃣0️⃣ Coding Snippets

The SharePoint Framework Toolkit comes together as a bundle with two other extensions. One of them is SPFx Snippets created by Elit Struyf.

It contains snippets for working in:

  • JavaScript (resource files)
  • React
  • SASS (SCSS)
  • TypeScript
  • JSON

In order to start using it simply start typing from spfx- and you should see a full list of snippets that will inject code into the current file.

code snippets

Check out the extension details to find out more

Check it out in action 👇

code snippets

1️⃣1️⃣ Teams Toolkit Integration

Teams Toolkit is a widely used VS Code extension that aims to help you develop solutions that will allow you to extend Microsoft Teams. SharePoint Framework Toolkit aims to boost your productivity in SharePoint Framework solutions that may be used to extend SharePoint, Microsoft Teams, Microsoft Viva Connections, Outlook, and Microsoft365.com. Among many awesome functionalities, Teams Toolkit allows you to create a project to extend Teams Tab with SPFx project, and that’s where both of those extensions may cooperate.

Teams Toolkit integration

Check out our docs for more details

1️⃣2️⃣ Node.js Version Manager Support

By default, the SharePoint Framework Toolkit will use the Node.js version that is installed on your machine. If you want to use a different version, you can use a Node.js Version Manager such as nvm or nvs. The SharePoint Framework Toolkit will detect the preferred version of Node.js if a .nvmrc file is present in the root of your project, and will use that version for all the actions.

You can use the settings to change which Node.js version manager you want to use. You may choose between nvm and nvs. If you wish to avoid using a Node.js version manager, you can set the value to none

1️⃣3️⃣ SPFx Toolkit GitHub Chat Participant

SPFx Toolkit chat

Now you may use SPFx Toolkit as a chat participant in GitHub Copilot chat extension. Simply, mention @spfx in the chat to ask dedicated questions regarding SharePoint Framework development.

SPFx Toolkit chat in action

@spfx is your dedicated AI Copilot that will help you with anything that is needed to develop your SharePoint Framework project. It has predefined commands that are tailored toward a specific activity for which you require guidance.

SPFx Toolkit chat commands

Currently, we support the following commands:

  • /setup - that is dedicated to providing information on how to setup your local workspace for SharePoint Framework development
  • /new - that may be used to get guidance on how to create a new solution or find and reuse an existing sample from the PnP SPFx sample gallery
  • /code - that is fine-tuned to provide help in coding your SharePoint Framework project and provides additional boosters like validating the correctness of your SPFx project, scaffolding a CI/CD workflow, or renaming your project, and many more.

Check out our docs for more details

⚙️ Architecture

SharePoint Framework Toolkit for Visual Studio Code is an abstraction layer on top of the SPFx Yeoman generator and CLI for Microsoft 365.

This means that the features and capabilities provided through this tool are available for any solution which has been built with SPFx.

📚 Wiki

For more information on how to use the extension, please refer to the wiki.

👩‍💻 Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to grant us the right to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

If you have ideas for new features or feedback, let us know by creating an issue in the issues list. Before you submit a PR with your improvements, please review our contributing guide.

🙋 Support

This project is a community lead extension provided by the Microsoft 365 and Power Platform Community members. Microsoft employees are closely involved in this work, but the solution is provided under the community brand without direct supportability channels from Microsoft.

👍 Community

Are you building experiences for Microsoft 365? - Everyone is welcome to join our Microsoft 365 and Power Platform Community efforts with community calls, samples and guidance. Join our weekly community calls for Microsoft 365 and Power Platform topics or engage with us on Discord. Everyone is welcome 🧡

🧾 Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

📄 Changelog

See the changelog for the latest changes.

😍 "Sharing is Caring"

Microsoft 365 & Power Platform Community

🔍 Additional resources

⚠️ Disclaimer

THIS CODE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.

vscode-viva's People

Contributors

adam-it avatar estruyf avatar github-actions[bot] avatar vesajuvonen avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

vscode-viva's Issues

💡Feature Idea - extensions and webpart samples view

💡 Idea

I was wondering maybe since the extension already allows to create webpart, extensions ect.

image

And we do have a lot of great community samples for those maybe we should create similar sample views for webparts and extensions like we have for the adaptive cards.

.... or is this out of scope for this extension 😉?

🐞 [Bug]: The extension reads sample data from dev branch not main

📝 Describe the bug

The problem is that the extension reads sample data from dev branch not main. We should update the endpoint

const SAMPLES_URL = 'https://raw.githubusercontent.com/pnp/vscode-viva/dev/data/';

it is quite low as for now we may run the flow manually against dev branch and update this as well

👣 Steps To Reproduce

Enter samples view and search for something recently added

📜 Expected behavior

Should show the latest samples added

💻 Desktop (please complete the following information):

  • Version v2

💡 [Feature]: Site design

💡Idea

This is probably out of scope 😜 but I was thinking of adding a totally new section to the action bar which would allow to manage site designs and site scripts using CLI for Microsoft 365 commands. So like

  • adding new site scripts to a site design
  • adding a site design
  • apply a site design to a site
  • checking the run list
  • etc...

reference commands
https://pnp.github.io/cli-microsoft365/cmd/spo/sitedesign/sitedesign-add/
https://pnp.github.io/cli-microsoft365/cmd/spo/sitedesign/sitedesign-add/

🐞 [Bug]: Upgrade action issue

📝 Error caused by newline characters in overrides JSON while upgrading SPFx solution using vscode-viva upgrade action

I am using vscode-viva to upgrade an SPFx solution. While updating the .eslintrc.js file as suggested in the upgrade report, I noticed an issue where newline characters ("\n") are being displayed as line breaks in the overrides JSON object. This is corrupting the file and causing the following error during the solution build.

Cannot read config file: C:\RnD\helloWorld\.eslintrc.js
Error: Invalid or unexpected token

👣 Steps To Reproduce

Steps to reproduce the behavior:

  1. Open Viva Connection Toolkit extension in a SPFX project (v.1.15.0)
  2. Click on the 'Upgrade' action.
  3. Follow the instruction in the spfx.upgrade.md report.
  4. Notice the line breaks in .eslintrc.js
    image

📜 Expected behavior

The value should be displayed without newline characters ("\n") interpreted as line breaks.
image

💻 Desktop (please complete the following information):

  • OS: Microsoft Windows 10.0.22000

🤔 Additional context

I am certain that it is a cli-microsoft365 issue, but I was unable to reproduce it with CLI v6.9.0. Therefore, logging the issue here.

💡 [Feature]: Add support for SPFx v1.18

🎯 Aim of the feature

The aim is to add support for SPFx v1.18

🤔 Additional remarks or comments

This is not GA yet and also not available in CLI for Microsoft 365 yet.

Release v2

We are getting ready to release v2. Let's go over the steps to be sure we don't miss anything
Release ToDo list:

  • update readme
  • update version
  • update changelog
  • merge to dev
  • align to main
  • release

🔧 Rapid clicking seems to hang the extension & extension size seems to be to big

👋
First of all congrats on the amazing work till now 🤩.
I did some first quick check. One thing I notices (I don't really think it is a bug but rather a strange behavior) is when we click on 'check dependencies' button, when it is 'checking' 😜, the samples or solutions webviews are not loading until the check finishes. Seems strange don't you think? I would expect we may work with the extension normally without having have to wait for the check to finish.

quickCheck.mp4

Let me know what do you think ?

💡Feature Idea - add help and feedback section with links to documentation and PnP community

💡 idea

Similar like the Teams Toolkit we could add help & documentation section in the side bar with the following links:

  • link to issues list to the repo
  • link to PnP community home page
  • link to SPFx MS docs page
  • link to the documentation to viva

It would be best if the links were read from some external JSON which is part of the project, so that in the future adding a new link will not need to modify the code but only some data.json file.

🖌️🎨Rebranding

🎯 Aim

The aim of this issue is to create new icons for the extension that will align it more to SharePoint Framework area. Currently, the icon is PnP VS Code which is really generic. It will make more sense to make it 'PnP SPFx' and 'PnP SharePoint Framework Extension'

💡Feature Idea - environment details could support adding site app catalog

💡 Idea

So currently environment details the extension shows just the tenant main site and the tenant app catalog

image

I was thinking we could add a feature that would allow the user to add additional environments to the list pointing to site level app catalogs. Then when deploy action is used and multiple envs (app catalogs) are present on the list, the user would need to first pick to which app catalog she or he wants to deploy the package. What do you think?

maybe even later on and additional feature could be to give the possibility to create a new app catalog on site level using the m365 spo site appcatalog add command

💡 [Feature]: Create a .devcontainer for SPFx solution

🎯 Aim of the feature

The extension could check if the current project has a .devcontainer and if not it could suggest generating one. Also this could be added as a new action (similar like the pipelines).
The added devcointaner could be based on those created in the pnp script sample repo.

🤔 Additional remarks or comments

We should recheck if the docker image used in the container may set any kind of SPFx version

Also we could first focus on this CLI for M365 issue to extend this as a new command in CLI first and then create it as a new action in viva toolkit
pnp/cli-microsoft365#3098

📢Work on marketing

🎯 Aim

The aim of this issue is to improve the marketing of the product. As a good start we could:

  • #17
  • Prepare guidance movies/gifs and marketing campaigns on LinkedIn and Twitter

Installation Problems

Two issues which i encountered while on Windows PC

  1. Installed the app in VSCode. The PNP icon started showing -> ok
  2. Created a new project using the Planner template . The source code was copied to my local drive but VS code gave the following error "File system provider for c:. is not available."
  3. I also could not open the newly created project in VSCode.

So uninstalled and installed the app again. But this time now the Pnp icon does not show up at all (see image)

Good idea btw :-)

installation

💡Feature Idea - extend extension component list

💡Idea

So currently if we would like to create an SPFx extension using vscode-viva we only see the app customizer, field customizer and list view command set. I would suggest to align it with latest and allow to add form customizer and search query modifier

image

💡 [Feature]: Manage cdn

💡 Idea

I was thinking to adding a totally new section/view to the activity bar "CDN" which would allow to manage Office 365 Content Delivery Network (CDN) with SharePoint Online (get, set, remove, set policy etc) cdn using CLI for Microsoft 365

For that we could use the following CLI commands
https://pnp.github.io/cli-microsoft365/cmd/spo/cdn/cdn-origin-add
https://pnp.github.io/cli-microsoft365/cmd/spo/cdn/cdn-origin-list
https://pnp.github.io/cli-microsoft365/cmd/spo/cdn/cdn-get/
... etc

docs
https://learn.microsoft.com/en-us/microsoft-365/enterprise/use-microsoft-365-cdn-with-spo?view=o365-worldwide

The main drawback is that we introduce additional view and the toolkit has already multiple views that take a lot of space 🤔. Maybe we should think of alternatives.

📝 Add Docs for features added as part of v2 and marketing materials

🎯 Aim

The aim is to extend current wiki docs and readme with features added as part of v2. Additionally add marketing materials (shorts, movies and images) for those features.

✅ Things ToDo:

  • wiki and readme: CI/CD pipeline
  • short: CI/CD pipeline
  • movie: CI/CD pipeline
  • wiki and readme: grant API permissions
  • movie: grant API permissions
  • wiki and readme: rename project
  • short: rename project
  • movie: rename project
  • wiki and readme: site collections support
  • movie: site collections support
  • wiki and readme: Code snippets

💡 [Feature]: Granting project API permissions

💡 Idea

since to CLI for Microsoft 365 we added a cool new command spfx project permissions grant which allows you to grant API permissions defined in the current SPFx project I was thinking it could be a nice addition to this extension.
in the Actions section
image

We could add a new action grant solution API permissions which when clicked would execute this new CLI for M365 command which just checks what is defined the webApiPermissionRequests section in package-solution.json file and grants those permissions. This is really cool as thanks to that we may continue developing/testing on workbench without the need to deploy the package to the tenant to be able to grant and confirm those permissions.

🐞 [Bug]: loging out and in shows an error message

📝 Describe the bug

When log in using the extension I get the error that I cannot get account details. Restarting VS resolves this issue
It happens on latest pre-release and when I have multiple VS Code opened

👣 Steps To Reproduce

Steps to reproduce the behavior:

  1. Go to the extension
  2. Click on logout and then login
  3. Proceed to with the steps in the browser

📜 Expected behavior

Should login me without any error and present the urls

📷 Screenshots

image

📄🤔 Improve Readme

The current readme info is very minimal. It provides a little description and there is nothing that catches they eye (only two screenshots) maybe we could add some gif's to present it in action or/and link to Vesa article or PnP Demo about this tool 🤔

🎥 Present the product on a PnP Community call

date: 02.11

plan for the demo (scenario-based):

  • how to install the extension from the marketplace and also get the pre-release version
  • validating dev environment and dependencies
  • welcome experience scaffolding new project based on sample
  • upgrade and validate project
  • login to tenant and checking what you see in environment section
  • gulp task to serve a webpart
  • grant api
  • deploy to app catalog
  • help section
  • extending project using SPFx snippets
  • create CI/CD flow and push to repo to check

New Project creation mode get stuck on Component name

On Mac machine, upon click of. "Create aVvia Connections projects", the extension asks first three question successfully but then gets stuck in "Component name is required".

Repeated press of enter key does not work, changing the default "Hello World" to something else also does not work

plz see the video

2022-06-01.15-45-53.mp4

💡Feature Idea - search options for samples/scenarios

💡 Idea

I was wondering would make sense to add some search functionality for the samples and scenarios view. I agree in scenarios currently we don't have much data but in samples it maybe makes more sense as now we need to search manually for the thing we are looking for and go between pages.

🎯 Aim

I would start with a simple input that would actually do filtering of data matching the title of the sample 🙂. What do you think?

📷 Mocked result

I created a very professional mockup how would I do it for now 🙂
image

⚙️ Repo maintenance

🎯 Aim

The aim is to improve repo maintenance, documentation and quality. As first good steps I should:

  • improve contributing guidance explaining which branch should be the target when opening a PR etc. #29
  • refactor the release beta process not to base on automatic numbering as now it is inconsistent with the change log and it is impossible to keep this aligned #27
  • make main a safe branch
  • make dev safe branch (only PR's allowed with bypass possible for PnP crew)
  • turn on dependabot
  • turn on codeQL
  • make dev default branch (at least until the official release)
  • Issues templates #26
  • PR templates #26

Epic: Product Marketing

🎯 Aim of the feature

The aim is to list out all actions that might help in the product:

  • release a 1.0 version of the product. This will create confidence in the product. In order to do that I am waiting for a green light (I guess @VesaJuvonen this one is on you 😉)
  • prepare short HOWTO movies presenting tool features
  • add more documentation about the product to make it easier to use and promote it #50
  • add a blog post going over the tool features -> pnp/blog#1348
  • #73

[Maintenance] - Extend Wiki

🎯 Aim

We should extend the wiki with:

  • detailed manual of the VS Code functionality
  • info about how it was developed and what is the approach and release flow
  • links to additional resources: links to blog posts, demos, everything

🐞 [Bug]: When no terminal has yet been opened, toolkit opens it and runs `ulp package-solution`

📝 Describe the bug

If I haven't yet run a gulp task, clicking the 'bundle' or 'package solution' actions will open a new Terminal window. It will then run the gulp command, but something goes wrong and it misses the first 'g' of 'gulp':

image

I have this every time I close the 'Gulp tasks' terminal window and click the action. If I run a new action with the gulp tasks terminal already open, no issue occurs.

👣 Steps To Reproduce

Open an spfx solution, execute an action (bundle or package solution)

💻 Desktop (please complete the following information):

  • OS: Windows
  • Browser: Edge
  • Version: v1.1.0

💡 [Feature]: Add more managing SPFx extensions functionality

🎯 Aim

The aim would be to extend the environment view of the extension to provide more functionalities which will allow to management of webparts and extension in all app catalogs on user tenant

image

Some of the activities could allow:

  • move the sharepoint main page link to the account view and rename it to tenant
    • show link to SharePoint admin page
    • show link to webApiPermissionManagement
  • present solutions deployed per app catalog #215
  • add tenant-wide view to see tenant-wide deployed application customizers
  • show and 'attach' form customizers to a specific content type

🤔 Other

Some reference commands:
https://pnp.github.io/cli-microsoft365/cmd/spo/applicationcustomizer/applicationcustomizer-add/
https://pnp.github.io/cli-microsoft365/cmd/spo/tenant/tenant-applicationcustomizer-add/
https://pnp.github.io/cli-microsoft365/cmd/spo/contenttype/contenttype-set/ (modify content type to set the form customizer on a specific form)
https://pnp.github.io/cli-microsoft365/cmd/spo/customaction/customaction-add/

🐞 [Bug]: Unable to connect to an account

📝 Describe the bug

Unable to connect to an account.

👣 Steps To Reproduce

Maybe I'm missing something but I'm not able to connect to my tenant from the account section:

  1. Install the Viva Connections Toolkit
  2. Access the toolkit home page
  3. The account section doesn't display a button to connect to an account

📜 Expected behavior

I should be able to connect to my M365 tenant from the account section.

📷 Screenshots

image

💻 Desktop (please complete the following information):

  • Viva Connections Toolkit v0.5.1
  • Visual Studio Code 1.77.3

🤔 Additional context

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.