Giter VIP home page Giter VIP logo

powerbi-desktop-samples's Introduction

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Data/Telemetry

This project collects usage data and sends it to Microsoft to help improve our products and services. Read our privacy statement to learn more.

Disable telemetry collection within Power BI Desktop

Disable telemetry, within Power BI Desktop, do the following.

  1. Select File > Options and settings > Options.

  2. Within the Options dialog, select Usage Data and then uncheck Help improve Power BI Desktop by sending usage information to Microsoft.

  3. Select Ok.

Monthly blog samples

Within the Monthly Desktop Blog Samples folder, you will find the sample PBIX files used that go along with the monthly blog/video updates.

Report samples

Within the Sample Reports folder, you will find different report samples that can help you explore Power BI.

Report theme JSON schema

Within the Report Theme JSON Schema folder, you will find JSON schemas that specify valid properties to be customized in a Power BI report. This schema can be used in external application development or as a direct reference "$schema" within your custom theme JSON files for validation. More information in the folder's README.md file.

powerbi-desktop-samples's People

Contributors

amandacofsky avatar emlisa avatar guyinacube avatar jeroenterheerdt avatar maggiesmsft avatar mi77 avatar microsoft-github-policy-service[bot] avatar microsoftopensource avatar msftgits avatar ruiromano avatar yelper avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

powerbi-desktop-samples's Issues

4 different locations for samples

It appears we have 4 different locations for samples

img

what's the difference between new-power-bi-samples vs powerbi-service-samples? can the adventureworks sales samples be nested in sample reports. See Suggestion below:

  • Sample Reports
    • _archive
      • powerbi-service-samples (old)
    • AdventureWorks Sales Sample
    • powerbi-service-samples (new)

@maggiesMSFT

Enumeration values are not valid for labelOrientation

When using the enumeration for labelOrientation, it yields an error.

"labelOrientation": "horizontal",
"labelOrientation": "vertical",

image

The Schema should have something like:

                          "labelOrientation": {
                            "type": "string",
                            "enum": [
                              "horizontal",
                              "vertical"
                            ],
                            "title": "Orientation"
                          },

(Not sure if your convention is caps or lower, and not sure which value is 0 and which is 1!)

Data for Sales & Returns Sample v201912.pbix

Hi,

Can you please upload the Excel files used to create the Sales & Returns Sample v201912.pbix. I extracted the data from the pbix but model has many queries with transformations applied in PQ. It would be very helpful to have the data. Right now the Excel files are in Miguel's dropbox.
image
Ideally, upload all the files to Github and re-publish the report with queries pointing to Github. Thanks !

Setting Property of DIN seems to set Times New Roman in Desktop

When setting a KPI card "Callout Value" to a Font of DIN in a theme file, loading into Desktop seems to present the Font as "Times New Roman"

Steps to Re-produce:

  1. Start a brand new Power BI Desktop file
  2. Create a KPI card value, add a measure and a date value to the Trend Axis

Default Callout value looks like it is DIN

image

  1. Create a theme file that only changes the Callout Value Font to "DIN"

image

See attached json file DIN Error.zip

  1. Upload theme file into desktop

Notice on the File Successful load screen the DIN format in in the dropdown menu appears to change from DIN

image

  1. Close the window and look at the KPI visual, Looks like Times New Roman
    image

  2. Go into the Font dropdown and change to DIN

Notice the visual corrects it's self and now shows the proper font of DIN

image

Microsoft PowerBI Desktop includes OpenSSL v3.0.9 DLLs which are vulnerable to 4 published Security Vulnerabilities

Hello,

I appreciate this is the Github repository for PowerBI-Desktop-Samples and not the PowerBI Desktop application, but as there does not seem to be a way to raise this issue with the PowerBI desktop developers directly I am hoping if I raise it here, someone will see this and action - maybe so we can see a new release of the product with the vulnerabilities fixed / removed?

I raised a report for security vulnerabilities which exist when the PowerBI Desktop application is installed - Frustratingly this was rejected by MSRC because I did not supply a POC (explodinghead):

It appears that you are reporting out of date libraries, but no proof of concept is provided. While there are risks associated with specific functionality within the library, it does not mean we are using the vulnerable codes within the library.
In order to investigate your report specifically, I will need a valid proof of concept (POC) ideally with images or video, the detailed steps to reproduce the problem, and how an attacker could use it to exploit another user.

This report is currently here: Microsoft PowerBI Desktop includes OpenSSL v3.0.9 DLLs which are vulnerable to 4 published Security Vulnerabilities

But, in case this ticket gets closed / removed - in my report I state:

Within the default install of Microsoft PowerBI Desktop (build: 2.123.742.0, (also affected 2.123.684.0 & 2.121.782.0)) there are 8 OpenSSL v3.0.9 DLLs which is currently vulnerable to 4 published CVEs

The specific CVE raised against this vulnerability report (CVE-2023-5363) affects Incorrect cipher key & IV length processing of MODERATE severity fixed on 24 October 2023

Under the default user install path, These files are found below here:
c:\program files\windowsapps\microsoft.microsoftpowerbidesktop_2.123.742.0_x64__8wekyb3d8bbwe\bin\odbc drivers\simba spark odbc driver\

Using the following Powershell to show the evidence

Get-ChildItem *libcrypt*.dll,*libssl*.dll,*openssl.exe -Recurse -Force -ErrorAction SilentlyContinue | Select-Object versioninfo -ExpandProperty versioninfo | Sort-Object ProductVersion,FileVersionRaw,Filename | Select-Object ProductVersion,FileVersionRaw,Filename | ft -auto

Returns the following results:

ProductVersion FileVersionRaw FileName
-------------- -------------- --------
3.0.9         3.0.9.0        c:\program files\windowsapps\microsoft.microsoftpowerbidesktop_2.123.742.0_x64__8wekyb3d8bbwe\bin\odbc drivers\simba spark odbc driver\libcurl64.dlla\openssl64.dlla\libcrypto-3-x64.dll
3.0.9         3.0.9.0        c:\program files\windowsapps\microsoft.microsoftpowerbidesktop_2.123.742.0_x64__8wekyb3d8bbwe\bin\odbc drivers\simba spark odbc driver\libcurl64.dlla\openssl64.dlla\libssl-3-x64.dll
3.0.9         3.0.9.0        c:\program files\windowsapps\microsoft.microsoftpowerbidesktop_2.123.742.0_x64__8wekyb3d8bbwe\bin\odbc drivers\simba spark odbc driver\openssl64.dlla\libcrypto-3-x64.dll
3.0.9         3.0.9.0        c:\program files\windowsapps\microsoft.microsoftpowerbidesktop_2.123.742.0_x64__8wekyb3d8bbwe\bin\odbc drivers\simba spark odbc driver\openssl64.dlla\libssl-3-x64.dll
3.0.9         3.0.9.0        c:\program files\windowsapps\microsoft.microsoftpowerbidesktop_2.123.742.0_x64__8wekyb3d8bbwe\bin\odbc drivers\simba trino odbc driver\libcurl64.dlla\openssl64.dlla\libcrypto-3-x64.dll
3.0.9         3.0.9.0        c:\program files\windowsapps\microsoft.microsoftpowerbidesktop_2.123.742.0_x64__8wekyb3d8bbwe\bin\odbc drivers\simba trino odbc driver\libcurl64.dlla\openssl64.dlla\libssl-3-x64.dll
3.0.9         3.0.9.0        c:\program files\windowsapps\microsoft.microsoftpowerbidesktop_2.123.742.0_x64__8wekyb3d8bbwe\bin\odbc drivers\simba trino odbc driver\openssl64.dlla\libcrypto-3-x64.dll
3.0.9         3.0.9.0        c:\program files\windowsapps\microsoft.microsoftpowerbidesktop_2.123.742.0_x64__8wekyb3d8bbwe\bin\odbc drivers\simba trino odbc driver\openssl64.dlla\libssl-3-x64.dll

Full list of OpenSSL v3.0 vulnerabilities are published here on the OpenSSL website: https://www.openssl.org/news/vulnerabilities-3.0.html

The current list of available (and supported) OpenSSL versions for download is here on the OpenSSL website: https://www.openssl.org/source/

These 3rd Party OpenSSL DLLs should to be updated to the latest available version with each new release of the PowerBI Desktop install to ensure you are not exposing your customers to existing vulnerabilities.

Maybe someone on the PowerBI development team can respond?

How to get the data for the Regional Sales Sample?

Hello,

I downloaded the Regional Sales Sample power BI and opened it by power BI desktop. But it looks i need to get credential to get the data.

Do you know how to get it? Thank you very much!

Source = Excel.Workbook(Web.Contents("https://microsoft-my.sharepoint.com/personal/misewell_microsoft_com/Documents/Documents/GitHub/ContosoBI/Contoso%20-%20Sales%20-%20Current%20Release/Contoso%20-%20Dynamics%20365%20Sales%20Source%20Data.xlsx"), null, true),

Canvas settings page size in custom theme file

According to the theme file json schema, there is a setting to control the type and size of the canvas (as in Format page/Canvas settings in Power BI Desktop). However, these settings (which adhere to the schema) does not propagate to Power BI:

{
    "name": "myName",
    "visualStyles": {
        "page": {
            "*": {
                "pageSize": [
                    {
                        "pageSizeTypes": "Custom",
                        "pageSizeWidth": 1920,
                        "pageSizeHeight": 1080
                    }
                ]
            }
        }
    }
}

Is this a bug, or pure incompetence on my side?

advancedSlicerVisual : value fontColor theme setting not applied

Using the March 2024 version of Power BI Desktop.
I am trying to set the default font color of the button values in the new button slicer visual, but the theme settings are not applied. Setting the font size, family is OK, but the following code does not affect the font color. I have also tried using theme colors, but to no avail. Is this a bug or am I missing something ?

"advancedSlicerVisual": { "*": { "value": [ { "show": true }, { "$id": "default", "fontFamily": "Segoe UI Semibold", "fontColor":{"solid": {"color":"#4A4A4A"}}, "fontSize": 10, "transparency": 0, "horizontalAlignment": "center" }, { "$id": "selected", "fontColor":{"solid": {"color":"#4A4A4A"}} } ] } }

blog demo

Where can I find these demos? Thanks.

Vertical Alignement enum refers horizontal alignment

the actionButton object does not have the right properties for verticalAlignment. It refers to the same enum as horizontalAlignment

"alignment": { "type": "string", "enum": [ "left", "center", "right" ]

This breaks our current theme since the value "middle" was accepted before, and IMO does not make sense with the values from any format setting (at least left and right do not make sense for verticalAlignment)

definition.pbir files for Live Connections change in the service

I created a report in Power BI Desktop that has a live connection to a published Power BI Dataset. I saved it as a Power BI Project and pushed it to Azure DevOps. I connected a new workspace to the Azure DevOps repo and the report appears. However, when I make a change in Power BI Desktop and update the repo, the report in the workspace changes status to Uncommited. If I commit from the workspace, the defintion.pbir file is changed. The connection string originally contained ';Access Mode=readonly' when it was created in Power BI Desktop. Committing from the workspace removes this from the connection string in the definition.pbir file. Will this be changed in the new report format mentioned in the blog?

[Performance Analyzer Export sample] Why does time other not exclude time direct query?

I am studying PerformanceAnalyzerExportReport.pbix for learning how to analyze the output of the performance analyzer.
I found the function for Time Other (ms) is Time Other (ms) =
[Time Total (ms)] - [Time DAX Query (ms)] - [Time Visual Display (ms)]
.
image
Why does it not exclude time direct query, i.e. Time Other (ms) =
[Time Total (ms)] - [Time DAX Query (ms)] - [Time Visual Display (ms)] - [Time Direct Query (ms)]
?

cardVisual -> Layout -> alignment should be verticalAlignment

Problem Description

For the Card(new) Visual PowerBI offers the option to specify a Vertical Alignment under "Format your Visual" -> "Visual" -> "Layout". The Options here are Top, Middle and Bottom.

However, in the reportThemeSchema-2.118.json the alignment property is defined as a regular alignment which is defined with the options Left, Center and Right.

Minimal Example to recreate the Problem

When i create a JSON Theme with the following JSON code, it can be loaded into Power BI but has no effect on the visual Card(new) -> Layout -> Vertical Alignment:

{
  "name": "Minimal Example",
  "visualStyles": {
    "cardVisual": {
      "*": {
        "layout": [
          {
            "alignment": "right",
            "orientation": 1,
            "cellPadding": 5
          }
        ]
      }
    }
  }
}

When i change "alignment": "right" to "alignment": "bottom" i can not load the Theme.

Suggestion on how to resolve the Problem

When i change the Vertical Alignment in Power BI under "Format your Visual" -> "Visual" -> "Layout" to "bottom" and save the file. It gets saved as "alignment":{"expr":{"Literal":{"Value":"'bottom'"}}} in the pbix file.

I belive replacing "$ref":"#/definitions/alignment" with "$ref":"#/definitions/verticalAlignment" for the "alignment" property would resolve this issue

Search for the following string to find the relevant spot in the json file:
"layout":{"type":"array","items":{"type":"object","properties":{"alignment":{"$ref":"#/definitions/alignment","title":"Alignment"}

Report theme JSON schema - Filter pane and card properties not consistent.

The JSON properties for the filter pane and cards are not consistent through the documentation and JSON schema.

https://github.com/microsoft/powerbi-desktop-samples/tree/main/Report%20Theme%20JSON%20Schema#report-theme-json-schema

Currently, formatting the filter pane and the cards must be done by mixing the "filter card property" of the visual styles that apply to all visuals and the "outspace pane" property of the Page object.

image

image

But according to the new JSON schema, this needs to be done through the "outspacePane" and "filterCard" properties of the "Page" object, some of the properties do not work.

image

Additionally, in the Schema, there is no documentation of the "state" (Available, applied) for the cards.

In advance, thanks for checking this.

@yelper

Changing the Color of Applied Filter Cards Broken

When trying to change the color of a Filter Pane Filter Card in the applied state the change does not do anything. I've attempted making the change using the customize current theme in PBI Desktop, but when I select apply nothing changes. Going back into the customize current theme editor and it shows the original color value.

I've also attempted changing the JSON file manually, however the same thing happens, it doesn't matter what the color entered is when loaded it always reverts back to the standard color.

the backgroundColor under the "Applied" ID is where i made the change manually. however when the theme is loaded into PBI Desktop the Customize Current theme editor shows the color as hex #F3F2F1 no matter how it is attempted to be changed.

Changing the "Available" background color is broken in the same way, no matter how you change it, it stays as white.
This appears to have happened with the most recent PBI Update.

"filterCard": [ { "$id": "Available", "backgroundColor": { "solid": { "color": { "expr": { "ThemeDataColor": { "ColorId": 6, "Percent": 0 } } } } }, "transparency": 0, "textSize": 10 }, { "$id": "Applied", "backgroundColor": { "solid": { "color": "#F0B310" } }, "transparency": 0, "textSize": 10 } ],

Bar chart switch axis not working

Each of the bar chart types have a switchAxisPosition item in both the categoryAxis and the valueAxis. Only the categoryAxis switches positions, though, which matches the user interface in Power BI Desktop.

I'm hoping this means switch axis might be coming to the value axis.

Is it possible to create a theme.json which can set a background image for a specific page?

I want to set a different background image per page. Is this possible? Currently I have

{
    "name": "Custom",
    "$schema": "https://raw.githubusercontent.com/microsoft/powerbi-desktop-samples/main/Report%20Theme%20JSON%20Schema/reportThemeSchema-2.115.json",
    "visualStyles": {
        "page": {
            "*": {
                "background": [
                    {
                        "image": {
                            "name": "Background",
                            "scaling": "Fit",
                            "url": "data:image/svg+xml,..."
                        },
                        "transparency": 1
                    }
                ]
            }
        }
    }
}

I've tried replacing the * with page name, displayname and index but it doesn't seem to affect anything (which makes sense, based on the schema).

Thanks

reportThemeSchema allow replacing white and black first two theme colors

Please consider allowing to replace first two theme colors (white and black) with off-white and off-black colors, as this is good design practice to avoid straight white and straight black colors when creating UI/Themes. I would appreciate being able to select my off- colors from palette

slicer orientation / style / mode enum list hasn't been updated to support the change to slicer orientation settings in PBI

Slicer 'Styles' were migrated from being in the visual header drop-down menu to now being in the 'Style' general formatting menu.

The JSON schema still only supports orientation enum options of 0 and 1 for vertical list vs horizontal tile orientations here and does not support the additional 'Style' options that now include things like making the slicer a drop-down list by default or a 'between', 'relative date', etc.

The {*} > {*} > {mode} in the json schema appears to list all these new style options but when I set define this way, it doesn't appear to be applying in-app.

 "mode": {
       "type": "string",
       "enum": [
                  "VerticalList",
                  "HorizontalList",
                  "Between",
                  "Before",
                  "After",
                  "Basic",
                  "Dropdown",
                  "Relative",
                  "Single",
                  "RelativeTime"
       ],
       "title": "Style" 

The {*} > {general} > {orientation} enums of 0 and 1 do still work to switch between VerticalList and HorizontalList, but don't accept any additional enum values that might represent Dropdown mode as far as I can tell.

Is there another way to set the slicer orientation / mode / style via json?

Shape fill and outline seeing theme settings

Using the following code, I still have the defaults from the report file coming in, text stay's as Segoe, and colour is my main colour choice (blue) not what is set below. Unless I am not doing it right.

Ideally the outcome should be a Shape with white fill, black border, Arial font.

        "shape": {
            "*": {
                "background": [
                    {
                        "show": false
                    }
                ],
                "border": [
                    {
                        "show": false
                    }                    
                ],
                "fill": [
                    {
                    "show": true,
                        "fillColor":{
                            "solid": {
                                "color":"#FFFFFF"
                            }                            
                        },
                        "transparency": 0
                    }
                ],
                "outline": [
                    {
                        "show": true,
                        "lineColor":{
                            "solid": {
                                "color":"#000000"
                            }
                        }
                    }
                ],
                "text": [
                    {
                        "fontFamily": "Arial",
                        "fontColor":{
                            "solid": {
                                "color":"#000000"                            
                            }
                        },
                        "fontSize": 10
                    }
                ]
            }
        }, 

"columnFormatting" property on tableEx not applied?

Hi,
I'm using the Dec 23 version of PBI Desktop and reportThemeSchema-2.124.json to setup my custom theme but the "columnFormatting" property on the tableEx visual doesn't seem to have any effects. Other properties like columnHeaders works. Any one else is facing this issue or am I missing something?
Thank you

actionButton "press" state not applying in Desktop

Since @yelper pointed out the different states for actionButton in #50 , I want to point out that neither pressed or press (as it used to be) have any effect inside Power BI Desktop - the visual defaults back to the default state.

I am currently on Power BI Desktop for Report Server (May 2023), so I should ask if others experience the same issue?

Example

(...)
		"actionButton": {
			"*": {
				"shadow": [
					{
						"show": true
					},
					{
						"$id": "default",
						"transparency": 0,
						"shadowBlur": 20,
						"shadowPositionPreset": "center"
					},
					{
						"$id": "hover",
						"transparency": 0,
						"shadowBlur": 20
					},
					{
						"$id": "press",
						"transparency": 95,
						"shadowBlur": 25
					},
					{
						"$id": "disabled",
						"transparency": 20,
						"shadowBlur": 0
					}
				]
			}
		}

ActionButton States

Couldn't really find the syntax for the different states for ActionButtons.
I might overseen it, is this supported ?

I now use:
`"actionButton": {
"*": {
"visualHeader": [{
"show": true
}],
"border": [{
"show": false
}],
"text":[{
"show":true
},
{
"$id": "default",
"transparency": 0,
"fontColor": {"solid":{"color":"#D91F43"}},
"fontFamily": "Arial",
"bold": false
},
{
"$id": "hover",
"transparency": 0,
"fontColor": {"solid":{"color":"#ffffff"}},
"fontFamily": "Arial",
"bold": false
},
{
"$id": "selected",
"transparency": 0,
"fontColor": {"solid":{"color":"#ffffff"}},
"fontFamily": "Arial",
"bold": false
}],

    }`

visualStyles/slicer/*/data/mode property doesn't work

Hi team,

I am setting my first JSON theme and I tried to configure the default mode of slicers set to "Dropdown" but it doesn't work.
Although I imported the theme to one report when I add a slicer it has different predefined style based on "data type" of the field. For example, for "Text" data type Slicer Style is "Vertical List" and for "Whole Number" is "Between".

Below you can see the code used if it helps:

"visualStyles": {
        "slicer": {
            "*": {
                "items": [
                    {
                        "background":{"solid": {"color": "#0096D6"}},
                        "fontColor":{"solid": {"color": "#F9FAFA"}}
                    }
                ],
                "data": [
                    {
                        "mode": "Dropdown"
                    }
                ]
            } 
        } 
    }

If any extra information is needed I am available.

Thanks in advance for your help and congratulations for the development of this amazing feature :)

Use of $schema

@yelper

After using $schema to test a theme, do you recommend keeping it in the theme to show the version used when developing the theme, or should this be removed before loading the theme to Power BI? If you leave it in, I assume Power BI will ignore it and use the latest schema.

Can you add the answer to the README.md page?

Also is there some sort of permalink to the most recent schema (eg. reportThemeSchema.json)? Right now it looks like the only file has a version number, eg. https://raw.githubusercontent.com/microsoft/powerbi-desktop-samples/main/Report Theme JSON Schema/reportThemeSchema-2.114.json

Report theme JSON schema - Accept comments

Hi, would it be possible to add a "comment" field to all the properties?

Before the big release of the new JSON themes, this was possible, unfortunately today, we can't add commments.

Sometimes naming is not intuitive, and it comes in handy for theme development. Thanks!

@yelper

image

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.