Sp-dev-docs: Office-ui-fabric-react in GA

Created on 24 Feb 2017 · 7Comments · Source: SharePoint/sp-dev-docs

Observed Behavior

Guys, first of all congrats with the GA release. Great job!

In the Release Notes, there is this line:

We have temporarily removed office-ui-fabric-react from the react template until we can get the package moved to a future-proof form. We expect that to take a couple of weeks.

What does this mean exactly? Can we no longer use it in React webparts (for now)? Or should we simply include the package ourselves when developing? And does this also mean we can include any version we want for now?

Thanks, and again: awesome job!

tracked

Source

NickSevens

👍2

Most helpful comment

Hi @NickSevens, we are about publish a more detailed advisory and the plan around office-ui-fabric-react soon. Will let you know when that is available.

manishgarg1 on 24 Feb 2017

👍4

All 7 comments

Hi @NickSevens, we are about publish a more detailed advisory and the plan around office-ui-fabric-react soon. Will let you know when that is available.

manishgarg1 on 24 Feb 2017

👍4

Thank you for the update @manishgarg1.

NickSevens on 24 Feb 2017

I managed to include and use fabric react on sp framework however encountered issue on including fabric components css.
https://github.com/OfficeDev/office-ui-fabric-react/issues/1162

jonathanhotono on 2 Mar 2017

@manishgarg1 any update on this?
Thank you.

NickSevens on 9 Mar 2017

Hi @NickSevens, we are working on documented guidelines how to use office-ui-fabric-react and office-ui-fabric in web parts. And also what are the options if you are not using React. Soon we should be able to share the white paper. Please note, due to global CSS all around and lack of native CSS scoping solutions in the browser, this is a non trivial problem.

manishgarg1 on 9 Mar 2017

Sorry for the delay. Doc is here - https://dev.office.com/sharepoint/docs/spfx/web-parts/guidance/office-ui-fabric-integration .

(Small update - hold off on this for a short while. Our build tools are a little too smart, and will convert static references into external ones. Getting that fixed and rolled).

patmill on 21 Mar 2017

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues