* Add Fluent CSS and Controls library (#1)
1. Added Azure IoT Fluent CSS and Controls library
2. Ran into compile errors with sass, so updated to latest version of node-sass, react-scripts and a few other packages to more closely align with baseline.
3. Turns out the JS files require the css file directly (instead of the scss), so had to update node-sass-chokidar and add a new importer to map ~ to node_modules. We should eventually remove the direct css import because react-scripts has built-in support for sass, but that requires touching >100 files so leaving that for a different PR.
4. Updated _themes.scss to import and extend the CSS library's colors, so we can start using its @themify mixin and color variables everywhere.
5. Updated the RM Shell component to use the Fluent Shell (which specifies a common way to support themes and RTL) as an example, and change some of its styling to use the fluent colors.
* Change _themes to use fluent colors
* Added more color fixes
* fix (#3)
* consolidate position of refresh bar
removed scrollbar customization
fix position of link on tiles
removed multiple loading on dashboard
* addressed PR comment
* Change select to fluent control (#5)
1. Change the RM Select component to use the fluent Select component.
2. Change the device group and time window dropdowns in the RM subheader to use the fluent 3. Select control instead of a custom dropdown.
4. Update to the latest fluent controls and css
5. Change the RM button component to match fluent css (migrating to the fluent controls caused too many breaks).
6. Change the input and button width+height to match the fluent size.
7. Remove the _normalize.scss import from index.scss - the fluent shell control supplies the same normalize file with some overrides to match the fluent styling, and importing it directly reverts some of them.
* migrate tooltip to consume Balloon Fluent Control
* Update refreshBar.scss
removed font-size
* migrate pivot to fluent controls
* added missing rem size
* updated the width
* Replace toggleBtn with fluent toggle control (#7)
* Change PCS Grid to match Fluent Management list (#6)
1. Change PCS Grid to match Fluent Management List
2. Change the device group and time select dropdown background colors to match that of the underlying panel, per Arturo.
3. Fix the text colors for the masthead in light theme.
* updated color on popup map panel
* Fix errors found in bugbash (#9)
1. Fix radio button group styling
2. Fix edit button position in rules edit panel
3. Fix tabIndex react error in packageNew component
* Migrate to Fluent Global Nav (#10)
* Change Flyout to use the Fluent Context Panel (#12)
* Change to use Fluent masthead (#13)
* Fix addNewFlyout.md
* Revert some unneeded changes to make the review easier
* Lock package versions and remove unused packages
* Align globalnav initialization to baseline to get a11y fixes
* Fix verticial alignment in grid
* Update to fluent controls v10
* Address review comments
* scss
* Basic Dashboard events
dashboard click, filters selected
* Add alert panel explore link event
* Add device group events
Add events for create/edit device groups
* Add rules page click event
* Add Help and Refresh events
add events for help dropdown. Also add event when refresh is clicked
* Add map click event
* Style fixes
Style fixes. Fix issue with new version of link--doesn't work for external links. Switch to <a> instead
* addressed comments
style fixes
* Remove unused code
* Address comments
style fixes, some renaming
* Use post request for long queries
If telemetry get request urls are longer than 2048 characters (happens if have many devices), send a POST request instead. Also remove devices from iot hub manager jobs query, as jobs cannot be filtered on devices and this query failed if the url got too long.
* Only post for long queries
Always use POST request for telemetry queries that include devices
dependabot[bot]
Elvin Morales
sushilraje
Isaac
Vishwam Subramanyam
Mary Ellen Chaffin
Molly Moen
Sang Hyun Kim
Avneet Singh