* Filtering sidebar and taging changes for Technology and solution areas tagging/filtering
- Modified item.json, api controller to have Tachnologies instead of types. Renamed Category to solution areas.
- Removed runtime version as now we have Functions 1.x and functions 2.x as first class technologies.
- Modified item.json to have language and technologies string as to be displayed in UI.
- Modifed sidebar and tags component to include all technologies, solution areas and languages.
* Like/Dislike button click: backend and UI changes
- Reused metric controller PUT api which is used to update download count for Like/dislike user action.
- Existing UpdateCounts function app updated to take care of Like count update.
- Added a new field named Likes in Library controller.
* Removed unused metrics as well as function repossible to calculate those metrics
* Separate stats-related properties into separate class
* Add CreatedDate property, removed AuthorType and AuthorTypeDesc
* Update id, createddate and author in items.json
* Update front-end application state when a new sample is successfully submitted to the back-end
* Add back-end validation for sample submission
* Use GitHub account name in app header if user has not provided a name in their GitHub profile
* Detail page stying
- Made sure scrollbar does not appear on detail page.
- Licence content is justified and max width is set to 750 px.
- Tab pane upper border line is now 100% width
* Add contributions page with conditional routing - user will be redirected to login page if they are not already logged in
* Use redux to manage login/logout state
List view page
-Added a reducer to hold states. Now there is one reducer(root reducer ) and state only holds samples.
The page is having a fixed header and side bar.
List view pane has a non scrollable fixed header.
The link from list view to detail page works, but detail page is not styled and action are not proper.
- If cosmos db endpoint is not present in application setting, items will be fetched from existing item.json
- Once cosmos db connection information is provided, first cosmos db initialization will start, which is taking items from item.json to cosmos db.
* Test commit into master
* Add 3 new templates
* Add two new languages
* Add new language filters
* Fix typo in url
* Add C# back
* Add new item
* New items
* Disable deploy button if sample does not have a deployment template
* python templates
* update to raw urla nd add missing props