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

Extensions: Support Development in Local Workbench #691

Closed
andrewconnell opened this Issue Jul 4, 2017 · 5 comments

Comments

Projects
None yet
3 participants
@andrewconnell
Collaborator

andrewconnell commented Jul 4, 2017

Category

  • Question
  • Typo
  • Bug
  • Additional article idea

Today, application extensions in SPFx (command sets, application customizers & field customizers) can't be tested within either the local or SharePoint Online hosted workbench. This is a bummer and a big step backwards to such a cool aspect to the development story with SPFx.

I get that you need a list to work with, but at a minimum, the workbench could have a static list with static data and no other functionality for us to test the customizations on.

My wish is that Microsoft adds support to the workbench for extensions before GA.

If you are planning to share a new feature request (enhancement / suggestion), please use SP Dev UserVoice at http://aka.ms/sp-dev-uservoice.

OK, cross-referenced: Extensions: Support Development in Local Workbench

@andrewconnell

This comment has been minimized.

Show comment
Hide comment
@andrewconnell

andrewconnell Jul 4, 2017

Collaborator

Closing to keep feature requests in UserVoice... my bad.

Collaborator

andrewconnell commented Jul 4, 2017

Closing to keep feature requests in UserVoice... my bad.

@Colbz

This comment has been minimized.

Show comment
Hide comment
@Colbz

Colbz Oct 20, 2017

Just starting to develop extensions now and realizing what a huge pain it is not having the local workbench. I have to retract and redeploy the solution every time I make a simple CSS change. We're back to farm solutions all over again. So inefficient

Colbz commented Oct 20, 2017

Just starting to develop extensions now and realizing what a huge pain it is not having the local workbench. I have to retract and redeploy the solution every time I make a simple CSS change. We're back to farm solutions all over again. So inefficient

@frankchen76

This comment has been minimized.

Show comment
Hide comment
@frankchen76

frankchen76 Oct 20, 2017

Have you checked Ignite video Building the modern SharePoint experience: Best practices from Microsoft for developing with SPFx ? It actually mentioned about an approach which you can add your SPO workbench with your customization properties into serve.josn, and then you can call gulp serve --config [your config] to open up your browser and go that url directly. You probably can find out the detail around 00:35:00 in the video. the following is a sample of serve.json:

serve json

you can run the following command
gulp serve --config customActions

frankchen76 commented Oct 20, 2017

Have you checked Ignite video Building the modern SharePoint experience: Best practices from Microsoft for developing with SPFx ? It actually mentioned about an approach which you can add your SPO workbench with your customization properties into serve.josn, and then you can call gulp serve --config [your config] to open up your browser and go that url directly. You probably can find out the detail around 00:35:00 in the video. the following is a sample of serve.json:

serve json

you can run the following command
gulp serve --config customActions

@Colbz

This comment has been minimized.

Show comment
Hide comment
@Colbz

Colbz Oct 20, 2017

Oh nice, this looks promising I will test and advise

Colbz commented Oct 20, 2017

Oh nice, this looks promising I will test and advise

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment