import { Dialog } from '@microsoft/sp-dialog/lib/index';

%3CLINGO-SUB%20id%3D%22lingo-sub-77600%22%20slang%3D%22en-US%22%3Eimport%20%7B%20Dialog%20%7D%20from%20'%40microsoft%2Fsp-dialog%2Flib%2Findex'%3B%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77600%22%20slang%3D%22en-US%22%3E%3CPRE%3E%26nbsp%3B%3C%2FPRE%3E%3CP%3Eso%20the%20%26nbsp%3Bddocumentation%20for%20spfx%20command%20sets%20says%20we%20should%3C%2FP%3E%3CP%3Eimport%20%7B%20Dialog%20%7D%20from%20'%40microsoft%2Fsp-dialog%2Flib%2Findex'%3B%3C%2FP%3E%3CP%3Eto%20display%20a%20dialog%20box.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ei%20thought%20we%20were%20supposed%20to%20be%20using%20fabric%20for.%20the%20ui.%26nbsp%3B%3C%2FP%3E%3CP%3Ewhat's%20up%20with%20that%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-77733%22%20slang%3D%22en-US%22%3ERe%3A%20import%20%7B%20Dialog%20%7D%20from%20'%40microsoft%2Fsp-dialog%2Flib%2Findex'%3B%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77733%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2387%22%20target%3D%22_blank%22%3EPieter%3C%2FA%3E%2C%3C%2FP%3E%3CP%3EAgreed.%3C%2FP%3E%3CP%3EI'm%20just%20curious%20if%20the%20spfx%20team%20is%20'wrapping'%20the%20fabric%20dialog%20component%2C%20and%20%26nbsp%3Bif%20so%2C%20will%20do%20the%20same%20for%20other%20fabric%20components%20going%20formward.%20Have%20not%20dug%20into%20it%20yet.%3C%2FP%3E%3CP%3ERussell%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-77731%22%20slang%3D%22en-US%22%3ERe%3A%20import%20%7B%20Dialog%20%7D%20from%20'%40microsoft%2Fsp-dialog%2Flib%2Findex'%3B%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77731%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F8901%22%20target%3D%22_blank%22%3E%40Russell%20Gove%3C%2FA%3E%2C%20One%20right%20doesn't%20mean%20that%20the%20other%20is%20wrong.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20dialogs%20you%20have%20quite%20a%20few%20options%20the%20option%20in%20this%20article%20by%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5720%22%20target%3D%22_blank%22%3E%40Vesa%20Juvonen%3C%2FA%3E%26nbsp%3Bis%20one%20way%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-docs%2Fblob%2Fmaster%2Fdocs%2Fspfx%2Fextensions%2Fget-started%2Fbuilding-simple-cmdset-with-dialog-api.md%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-docs%2Fblob%2Fmaster%2Fdocs%2Fspfx%2Fextensions%2Fget-started%2Fbuilding-simple-cmdset-with-dialog-api.md%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERecently%20for%20one%20of%20my%20customer%20I%20developed%20a%20custom%20form%20solution%20within%20a%20TypeScript%20SPFx%20web%20part.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fveenstra.me.uk%2F2017%2F06%2F05%2Foffice-365-sharepoint-how-to-create-forms-using-spfx%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fveenstra.me.uk%2F2017%2F06%2F05%2Foffice-365-sharepoint-how-to-create-forms-using-spfx%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20nice%20thing%20about%20the%20SPFx%20is%20that%20you%20can%20use%20any%20framework%20you%20like%20just%20add%20it%20with%20npm%20to%20your%20project%20and%20off%20you%20go.%20No%20real%20limitations%20just%20a%20lot%20of%20options.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20far%20I've%20found%20it%20a%20great%20way%20to%20say%20to%20my%20customers%20%22almost%20anything%20is%20possible%22.%20If%20it%20doesn't%20exist%20yet%2C%20then%20simply%20start%20from%20scratch%20and%20with%20simple%20TypeScript%20development%20you%20could%20build%20the%20forms%20%2C%20dialogs%20etc.%20it%20all%20depends%20on%20your%20requirements.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20Vesa's%20article%20%26nbsp%3Byou%20will%20find%20one%20of%20these%20options.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor
 

so the  ddocumentation for spfx command sets says we should

import { Dialog } from '@microsoft/sp-dialog/lib/index';

to display a dialog box.

 

i thought we were supposed to be using fabric for. the ui. 

what's up with that?

 

2 Replies
Highlighted

@Russell Gove, One right doesn't mean that the other is wrong. 

 

For dialogs you have quite a few options the option in this article by @Vesa Juvonen is one way:

 

https://github.com/SharePoint/sp-dev-docs/blob/master/docs/spfx/extensions/get-started/building-simp...

 

Recently for one of my customer I developed a custom form solution within a TypeScript SPFx web part.

https://veenstra.me.uk/2017/06/05/office-365-sharepoint-how-to-create-forms-using-spfx/

 

The nice thing about the SPFx is that you can use any framework you like just add it with npm to your project and off you go. No real limitations just a lot of options. 

 

So far I've found it a great way to say to my customers "almost anything is possible". If it doesn't exist yet, then simply start from scratch and with simple TypeScript development you could build the forms , dialogs etc. it all depends on your requirements. 

 

In Vesa's article  you will find one of these options.

 

 

 

Highlighted

Hi Pieter,

Agreed.

I'm just curious if the spfx team is 'wrapping' the fabric dialog component, and  if so, will do the same for other fabric components going formward. Have not dug into it yet.

Russell