-
Notifications
You must be signed in to change notification settings - Fork 1
v2.0.0
The 2.0.0 update is pretty significant and may contain breaking changes, so this page was set up to document primary steps to be taken by the PCP dev team to implement changes and new features.
The Short Answer is https://github.com/USDA-FSA/pcp/milestone/1?closed=1. The Detailed answer is below, they are either New features or Updated items.
I would tackle the updates/changes first to avoid conflicts - most are very simple - before diving into the new features.
- Sharepoint UX Prototype directory
- or PCP repo's Releases
Follow the steps listed on fsa-style dependency
Do NOT the below until you've successfully updated fsa-style
. The below "Updated" items below are pretty simple, often just search-and-replace.
The general rule of <a>
vs <button>
: if it goes somewhere, it's an <a>
; if it invokes an action, it's a <button>
. However, SPA by design can break those semantics significantly. So for those instances where it should look like a link, but act like a button, then go ahead and make it a button. For PCP, I suppose you also define that as "if the <a>
doesn't have a valid href
value but needs to look like a link, do the below."
The best example is the *Name column in Settings. There may be others in the app, so consider doing the below where necessary.
Replace...
<a href="link.html">text</a>
...with...
<button type="button" class="fsa-btn fsa-btn--flat">text</button>
- https://github.com/USDA-FSA/pcp/issues/9 and https://github.com/USDA-FSA/pcp/issues/38
- Screencast
- UX Prototype:
Newly-delivered design features.