Giter Site home page Giter Site logo

openapi-specification's Introduction

Google Maps Platform OpenAPI3 Specification

Build Release GitHub contributors semantic-release

Description

An OpenAPI specification for Google Maps Platform APIs.

API Status
Elevation Complete
GeoCoding Complete
GeoLocation Complete
Distance Complete
Roads Complete
Time Zone Complete
Directions Complete
Places Complete
Street View Complete
Maps Static Not Started

Note: New APIs will be documented using Google Discovery documents and Protobuf files.

Run in Postman

Development

The repository makes use of Bazel to generate outputs from the specification and sample requests.

Build and test

  1. npm i

  2. npm run build

    This generates the following outputs in the dist folder:

    • YAML file containing OpenAPI3 specification
    • JSON file containing OpenAPI3 specification
    • Structure Markdown documents for specification objects
    • Code snippets in multiple languages for sample requests

    Note: There is a bot that can be triggered in a pull request with a comment containing /update-dist. See the workflow at https://github.com/googlemaps/openapi-specification/blob/main/.github/workflows/command.yml.

    Note: The dist/ folder is included in this repo and should be updated with all changes.

    Note: If a documentation item is not generated, be sure it is included in the appropriate index.yml file.

  3. npm run responses (optional)

    Note: This is an optional step requiring an API key. Set the GOOGLE_MAPS_API_KEY environmental variable before running.

    Note: This step only needs to run when the generation code or sample requests have been updated.

    Note: The geolocation request that only provides an IP is not deterministic and skipped in the binary executed.

    Note: A single response can be updated similar to npm run responses -- --only maps_http_places_nearbysearch.

  4. npm run test

openapi-specification's People

Contributors

amuramoto avatar bamnet avatar barbeau avatar dependabot[bot] avatar googlemaps-bot avatar jaffourt avatar jpoehnelt avatar leslischauf avatar miguev avatar nora-soderlund avatar semantic-release-bot avatar sgilsonapigee avatar tranceraver avatar ubamrein avatar wangela avatar willum070 avatar zulu-capwn 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

openapi-specification's Issues

[parameters] Bug - /maps/api/directions/json

Steps to reproduce

  1. Add this in an iframe with an API Key
    https://www.google.com/maps/embed/v1/directions?origin=Tyne Tunnel Trade Park, Tyne Tunnel Trading Estate, Unit 3 Narvik Way, North Shields NE29 7DE&destination=Tyne Tunnel Trade Park, Tyne Tunnel Trading Estate, Unit 3 Narvik Way, North Shields NE29 7DE&waypoints=optimize:true|Barossa+Valley,SA|Clare,SA|Connawarra,SA|McLaren+Vale,SA&key=YOUR_API_KEY

Doesn't optimize the route instead it adds another waypoint to True Track Software Ltd, Office 9-10, Cauldon Locks, Shelton New Rd, Stoke-on-Trent ST4 7AB, United Kingdom.

Following these steps will guarantee the quickest resolution possible.

Thanks!

[parameters] Bug - /maps/api/place/autocomplete/json

Thanks for stopping by to let us know something could be better!


PLEASE READ

If you have a support contract with Google, please create an issue in the support console. This will ensure a timely response.

Discover additional support services for the Google Maps Platform, including developer communities, technical guidance, and expert support at the Google Maps Platform support resources page.

If your bug or feature request is not related to this particular library, please visit the Google Maps Platform issue trackers.

Check for answers on StackOverflow with the google-maps tag.


Please be sure to include as much information as possible:

Environment details

  1. Specify the API at the beginning of the title (for example, "Places: ...")
  2. OS type and version
  3. Library version and other environment information

Steps to reproduce

  1. ?

Code example

# example

Stack trace

# example

Following these steps will guarantee the quickest resolution possible.

Thanks!

[schemas] Bug - LatLngLiteral

Thanks for stopping by to let us know something could be better!


PLEASE READ

If you have a support contract with Google, please create an issue in the support console. This will ensure a timely response.

Discover additional support services for the Google Maps Platform, including developer communities, technical guidance, and expert support at the Google Maps Platform support resources page.

If your bug or feature request is not related to this particular library, please visit the Google Maps Platform issue trackers.

Check for answers on StackOverflow with the google-maps tag.


Please be sure to include as much information as possible:

Environment details

  1. Specify the API at the beginning of the title (for example, "Places: ...")
  2. OS type and version
  3. Library version and other environment information

Steps to reproduce

  1. ?

Code example

# example

Stack trace

# example

Following these steps will guarantee the quickest resolution possible.

Thanks!

[schemas] Bug - PlacesDetailsStatus

Thanks for stopping by to let us know something could be better!


PLEASE READ

If you have a support contract with Google, please create an issue in the support console. This will ensure a timely response.

Discover additional support services for the Google Maps Platform, including developer communities, technical guidance, and expert support at the Google Maps Platform support resources page.

If your bug or feature request is not related to this particular library, please visit the Google Maps Platform issue trackers.

Check for answers on StackOverflow with the google-maps tag.


Please be sure to include as much information as possible:

Environment details

  1. Specify the API at the beginning of the title (for example, "Places: ...")
  2. OS type and version
  3. Library version and other environment information

Steps to reproduce

  1. ?

Code example

# example

Stack trace

# example

Following these steps will guarantee the quickest resolution possible.

Thanks!

Places API Places Search: Nearby Places

radius is linked under "Optional Parameters" on the docs page but towards the bottom of the page in “Status codes returned by service” it's listed as being a possible reason for the INVALID_QUERY status code if it's missing due to being a required query parameter-- alongside location which IS listed as a necessary parameter
Screen Shot 2022-02-02 at 8 41 09 PM
Screen Shot 2022-02-02 at 8 40 19 PM
Screen Shot 2022-02-02 at 8 41 26 PM

Places: FindPlace API Bug using circle option for location bias

Steps to reproduce

  1. In postman, trying to call findplacefromtext, in order to find an airport near the specified coordinates, I am receiving a strange response. Even if the coordinates are from France, the API returns me an airport from Bucharest (my current location). It seems that the circle parameter for location bias is no longer taken into account.
    Worth to mention: This search API was working as expected until few days ago

Code example

https://maps.googleapis.com:443/maps/api/place/findplacefromtext/json?key=<mykey>&input=airport&inputtype=textquery&locationbias=circle%3a50000%4048.856614%2c2.3522219&fields=name&language=en

Response

{
    "candidates": [
        {
            "name": "Bucharest Băneasa - Aurel Vlaicu International Airport"
        }
    ],
    "status": "OK"
}

Thanks!

Distance is not returning miles even if units=imperial

Currently, we have a method that gets the distance matrix from google distance api.

    public async Task<DistanceMatrix?> GetDistanceMatrix(List<string> rawDestinationAddress,
                                                            string rawOrigin,
                                                            string travelMode = "DRIVING",
                                                            string unitSystem = "imperial")
    {
        var destinationAddress = JsonSerializer.Serialize(rawDestinationAddress.Select(x => HttpUtility.UrlEncode(x)));

        string url = @$"api/distancematrix/json?origins={HttpUtility.UrlEncode(rawOrigin)}
                                                &destinations={destinationAddress}
                                                &travelMode={travelMode}
                                                &units={unitSystem}
                                                &key={Config.Key}";
        
        return await HttpClient.GetFromJsonAsync<DistanceMatrix>(url);
    }

Even though we're sending in units=imperial, we always get km in distance.text.

Note: We have tested it just using browser and in there, it returns miles but when we use it in our project, we always get km.

May we know what's the right value for units?

Places: Autocomplete - Missing field "distance_meters" in PlaceAutocompleteResponse

Steps to reproduce

  1. Make a request to Places autocomplete api e.g. to https://maps.googleapis.com/maps/api/place/autocomplete/json?input=voortrekker%20monument&location=-26.204,28.0473&origin=-26.204,28.0473&key=key for a tourist site in South Africa. Notice how an origin is set.
  2. You'll get a response similar to this
{
 "predictions" : [
    {
       "description" : "Voortrekker Monument, Eeufees Road, Groenkloof 358-Jr, Pretoria, South Africa",
       "distance_meters" : 49264,
       "matched_substrings" : [
          {
             "length" : 20,
             "offset" : 0
          }
       ],
       "place_id" : "ChIJNSI5EExilR4RlDDAbNks5s0",
       "reference" : "ChIJNSI5EExilR4RlDDAbNks5s0",
       "structured_formatting" : {
          "main_text" : "Voortrekker Monument",
          "main_text_matched_substrings" : [
             {
                "length" : 20,
                "offset" : 0
             }
          ],
          "secondary_text" : "Eeufees Road, Groenkloof 358-Jr, Pretoria, South Africa"
       },
       "terms" : [
          {
             "offset" : 0,
             "value" : "Voortrekker Monument"
          },
          {
             "offset" : 22,
             "value" : "Eeufees Road"
          },
          {
             "offset" : 36,
             "value" : "Groenkloof 358-Jr"
          },
          {
             "offset" : 55,
             "value" : "Pretoria"
          },
          {
             "offset" : 65,
             "value" : "South Africa"
          }
       ],
       "types" : [ "tourist_attraction", "point_of_interest", "establishment" ]
    },
  etc, etc
 ],
 "status" : "OK"
}

The response contains a "distance_meters" field. The docs for the origin parameter say that a distance will be returned when an origin is provided.

We're using v1.17.10 of the spec and the "distance_meters" field in the response is missing.

Thanks.

[schemas] Bug - DirectionsGeocodedWaypoint

Steps to reproduce

  1. Call the directions API like this : https://maps.googleapis.com/maps/api/directions/json?destination=place_id:ChIJiQ-s2miw6kcR5dHaFfFdV9A&origin=place_id:ChIJO_mLi3UmwkcRqh4KYzJsypE&mode=transit&transit_mode=rail&alternatives=true&key=O_O
  2. Observe that the object geocoded_waypoints contains the type "train_station"
  3. This type shouldn't be there or should be supported : https://developers.google.com/maps/documentation/directions/get-directions#DirectionsGeocodedWaypoint (not mentioned here)
  4. The value "train_station" is not present inside the .yml but all possible other values are

Thanks!

DistanceMatrixApi is sending comma's between multiple points instead of pipes...

Thanks for stopping by to let us know something could be better!


PLEASE READ

If you have a support contract with Google, please create an issue in the support console. This will ensure a timely response.

Discover additional support services for the Google Maps Platform, including developer communities, technical guidance, and expert support at the Google Maps Platform support resources page.

If your bug or feature request is not related to this particular library, please visit the Google Maps Platform issue trackers.

Check for answers on StackOverflow with the google-maps tag.


Please be sure to include as much information as possible:

Environment details

  1. DistanceMatrixApi
  2. Window 10 Pro
  3. v1.17.6 of the specification

Steps to reproduce

  1. Calling method public async System.Threading.Tasks.Task DistanceMatrixAsync (List destinations, List origins, decimal? arrivalTime = null, decimal? departureTime = null, string avoid = null, string units = null, string language = null, string mode = null, string region = null, string trafficModel = null, string transitMode = null, string transitRoutingPreference = null)
  2. Passing in the 2 destinations of coordinates
  3. the Url constructed has comma between the destination coordinates instead of "|" pipe delimited. Fails call to google api

Code example

        List<string> destinationList = request.DestinationPoints.Select(s => s.ToString()).ToList();
        List<string> originList = request.StartPoints.Select(s => s.ToString()).ToList();
        var data = await _googleDistanceMatrix.DistanceMatrixAsync(destinationList, originList);
        return data;
# example
[```](https://maps.googleapis.com/maps/api/distancematrix/json?destinations=42.7101%2C-78.8026%2C42.991077%2C-78.759279&origins=43.004179%2C-78.751965&key=)



Following these steps will guarantee the quickest resolution possible.

Thanks!

Distance Matrix url has "/maps/api/distanceMatrix/json" should be "/maps/api/distancematrix/json". Was receiving a 404 not found

Thanks for stopping by to let us know something could be better!


PLEASE READ

If you have a support contract with Google, please create an issue in the support console. This will ensure a timely response.

Discover additional support services for the Google Maps Platform, including developer communities, technical guidance, and expert support at the Google Maps Platform support resources page.

If your bug or feature request is not related to this particular library, please visit the Google Maps Platform issue trackers.

Check for answers on StackOverflow with the google-maps tag.


Please be sure to include as much information as possible:

Environment details

  1. DistanceMatrixApi
  2. Windows 10
  3. [v1.17.6]

Steps to reproduce

  1. Calling DistanceMatrixApi

Code in specification

"/maps/api/distanceMatrix/json": { "get": { "operationId": "distanceMatrix", "servers": [ { "url": "https://maps.googleapis.com" } ], "tags": [ "Distance Matrix API" ], "description": "The Distance Matrix API is a service that provides travel distance and time for a matrix of origins and destinations. The API returns information based on the recommended route between start and end points, as calculated by the Google Maps API, and consists of rows containing duration and distance values for each pair.", "parameters": [ { "$ref": "#/components/parameters/arrival_time" }, { "$ref": "#/components/parameters/departure_time" }, { "$ref": "#/components/parameters/distancematrix_avoid" },

# example

Stack trace

# example

Following these steps will guarantee the quickest resolution possible.

Thanks!

Add links to generated documentation in README

The README for this repo lists the APIs and provides a link to Postman, but if I would like to browse rendered documentation it would be helpful to know where I can see the rendered docs.

Perhaps adding a column to the table in https://github.com/googlemaps/openapi-specification/blob/main/README.md#description with links to the corresponding pages in https://developers.google.com/maps/documentation/ would be the most straightforward way to do this.

Various links pointing to Google's internal docs

GoogleApi OpenAPI 3 YAML Specification

Issue

When making a request to the Google Autocomplete API A 500 internal error is being thrown by the when the JSON object is being deserialized. The following properties are required in the PlaceAutocompleteStructuredFormat object:

  • secondary_text
  • main_text_matched_substrings
    However Google Autocomple API does not always return these properties in the json model, which is causing the 500 internal error.

Environment details

  • OpenApi version: 1.17.17
  • PlaceAutocompleteStructuredFormat

Language and framework

  • Dotnet c#

Steps to reproduce

  1. Request to Google API Autocomplete
  2. Google Autocomple API does not always return a secondary_text or main_text_matched_substrings in the JSON response
  3. When the JSON response is being deserialized a 500 status code error is being thrown

Code example

try { return JsonConvert.DeserializeObject(response.Content, type, _serializerSettings); } catch (Exception e) { throw new ApiException(500, e.Message); } }

Stack trace

Screenshot 2022-09-09 113918

Several APIs: Some properties are missing a type

Sorry for deleting your nice template. If there isn't an obvious solution to this, I'll come back and fill out the full template. For now the file is just too big to parse out the exact details you require, and the issue is relatively simple and widespread.

Some properties are missing a type.

For example:

on line 23140:

steps:
          description: Contains detailed directions for walking or driving steps in transit directions. Substeps are only available when travel_mode is set to "transit". The inner steps array is of the same type as steps.

And, on line 23288:

partial_match:
          description: |
            Indicates that the geocoder did not return an exact match for the original request, though it was able to match part of the requested address. You may wish to examine the original request for misspellings and/or an incomplete address.

            Partial matches most often occur for street addresses that do not exist within the locality you pass in the request. Partial matches may also be returned when a request matches two or more locations in the same locality. For example, "21 Henr St, Bristol, UK" will return a partial match for both Henry Street and Henrietta Street. Note that if a request includes a misspelled address component, the geocoding service may suggest an alternative address. Suggestions triggered in this way will also be marked as a partial match.

This understandably trips up some code generators.

Is this expected behavior?

PlacesSearch/SearchNearby:: PlacePhoto - [bug]: Documentation error

Thanks for stopping by to let us know something could be better!


PLEASE READ

If you have a support contract with Google, please create an issue in the support console. This will ensure a timely response.

Discover additional support services for the Google Maps Platform, including developer communities, technical guidance, and expert support at the Google Maps Platform support resources page.

If your bug or feature request is not related to this particular library, please visit the Google Maps Platform issue trackers.

Check for answers on StackOverflow with the google-maps tag.


Please be sure to include as much information as possible:

Environment details

  1. Specify the API at the beginning of the title (for example, "Places: ...")
  • Done
  1. OS type and version
  • NA
  1. Library version and other environment information
  • "Last updated 2021-09-29 UTC."

Steps to reproduce

  1. https://developers.google.com/maps/documentation/places/web-service/search-nearby
  2. Under PlacePhoto
  3. See how example API call contradicts the required parameters for the call

Code example

https://maps.googleapis.com/maps/api/place/photo?maxwidth=400&photo_reference=photo_reference&key=YOUR_API_KEY
Field Required Type Description
height required number The height of the photo.
html_attributions required Array The HTML attributions for the photo.
photo_reference required string A string used to identify the photo when you perform a Photo request.
width required number The width of the photo.

Following these steps will guarantee the quickest resolution possible.

Thanks!
Screen Shot 2021-10-03 at 9 59 28 PM

[schemas] Bug - PlaceEditorialSummary didn't return

I follow this thread,
but I still can't see editorial_summary in the response.
Did I miss something?

Environment details

  • OS type and version
    macOS Ventura version 13.0.1

Steps to reproduce

I'm using New York for testing, which place_id is ChIJOwg_06VPwokRYv534QaPC8g.

curl https://maps.googleapis.com/maps/api/place/details/json\?place_id\=ChIJOwg_06VPwokRYv534QaPC8g\&fields\=editorial_summary\&key\=<key>

Stack trace

curl https://maps.googleapis.com/maps/api/place/details/json\?place_id\=ChIJOwg_06VPwokRYv534QaPC8g\&fields\=editorial_summary\&key\=<key>
{
   "html_attributions" : [],
   "result" : {},
   "status" : "OK"
}

DistanceMatrix : Api does not work because of how it is capitalized

Environment details

  1. Specify the API at the beginning of the title (for example, "Places: ...")
    Distance matrix api on postman

  2. Library version and other environment information
    1.17.10. I imported the collection from https://developers.google.com/maps/documentation/distance-matrix/start?hl=en_US#maps_http_distancematrix_start-postman

Steps to reproduce

  1. Import the collection to postman
  2. Add a destionation to the distancematrix query : https://maps.googleapis.com/maps/api/distanceMatrix/json?destinations=Washington%2C%20DC&origins=New%20York%20City%2C%20NY
  3. Send

Expected : Receive a response to my query since this is the happy path

Actual : I receive an error page
image

It seems that in the provided collection, the capitalization of the word distanceMatrix is wrong. To prove this, if you try this request instead, it works fine : https://maps.googleapis.com/maps/api/distancematrix/json?destinations=Washington%2C%20DC&origins=New%20York%20City%2C%20NY
image

[schemas] Bug - PlacesAutocompleteStatus

Thanks for stopping by to let us know something could be better!


PLEASE READ

If you have a support contract with Google, please create an issue in the support console. This will ensure a timely response.

Discover additional support services for the Google Maps Platform, including developer communities, technical guidance, and expert support at the Google Maps Platform support resources page.

If your bug or feature request is not related to this particular library, please visit the Google Maps Platform issue trackers.

Check for answers on StackOverflow with the google-maps tag.


Please be sure to include as much information as possible:

Environment details

  1. Specify the API at the beginning of the title (for example, "Places: ...")
  2. OS type and version
  3. Library version and other environment information

Steps to reproduce

  1. https://maps.googleapis.com/maps/api/place/queryautocomplete/json?key=xxxxxxxxx&language=en&components=country%3Aus&input=w
    Always return
    {
    "predictions": [],
    "status": "UNKNOWN_ERROR"
    }

Code example

# example

Stack trace

# example

Following these steps will guarantee the quickest resolution possible.

Thanks!

Places API radius doesn't work in text search

Environment details

image

Steps to reproduce

  1. radius get ignored in the request below
  2. It shows New York place data

Code example

const URI = encodeURI
(
https://maps.googleapis.com/maps/api/place/textsearch/json?query=%22best%20Internist%22&key=secret&fileds=place_id,formatted_address,name,rating,opening_hours/open_now,geometry,business_status,price_level,pagetoken,photos&language=en-us&location=52.516282,13.3131672&radius=5000
);
  
const { data } = await axios(URI, {
method: 'GET',
});

Places: FindPlace API [parameters] Bug - /maps/api/place/findplacefromtext/json

Steps to reproduce

  1. In postman, trying to call findplacefromtext with utc_offset as a field yet the documentation says utc_offset is an option

Code example

https://maps.googleapis.com/maps/api/place/findplacefromtext/json?fields=formatted_address,name,geometry,utc_offset&input=CN%20Tower,%20Toronto,%20Ontario&inputtype=textquery&key=<mykey>

Stack trace

{
    "candidates": [],
    "error_message": "Error while parsing 'fields' parameter: Unsupported field name 'utc_offset'. ",
    "status": "INVALID_REQUEST"
}

Following these steps will guarantee the quickest resolution possible.

Thanks!

chore: typo fix

There is a small typo in the docs of the nearby search endpoint, under the optional parameters "keyword".

Example

Places: FindPlace API Bug - locationrestriction & locationbias not working

Steps to reproduce

  1. In Postman, trying to call findplacefromtext api, providing the input 'london' and specifying a location restriction of within 10000 meters of the coordinates of London, Ontario, Canada still returns the result London, England

Code example

  https://maps.googleapis.com/maps/api/place/findplacefromtext/json?key=<mykey>&inputtype=textquery&locationrestriction=circle:[email protected],-81.2452768&input=london&fields=place_id,name,formatted_address

Response

{
    "candidates": [
        {
            "formatted_address": "London, UK",
            "name": "London",
            "place_id": "ChIJdd4hrwug2EcRmSrV3Vo6llI"
        }
    ],
    "status": "OK"
}

Swapping locationrestriction with locationbias here, it also returns London, UK. I would somewhat expect locationbias to return London, Ontario, Canada, but I understand it depends on how strong the location bias is.

However, I fully expect locationrestriction to return the 'london' that is within the location constraint provided.

I also tried specifying a rectangle for locationrestriction, but that did not work either.

optional parameters that aren't really optional for most use cases

Steps to reproduce

The The Places api Nearby Search documentation says that radius is an optional parameter. However, when I make a request without the radius parameter I get a response with "status" : "INVALID_REQUEST"

Code example

should be valid:

https://maps.googleapis.com/maps/api/place/nearbysearch/json?keyword=cruise&location=-33.8670522%2C151.1957362&type=restaurant&key=YOUR_API_KEY

{
   "html_attributions" : [],
   "results" : [],
   "status" : "INVALID_REQUEST"
}

is valid and returns valid results

https://maps.googleapis.com/maps/api/place/nearbysearch/json?keyword=cruise&location=-33.8670522%2C151.1957362&type=restaurant&key=YOUR_API_KEY&radius=1000

Add "FUTURE_OPENING" to the business status enum

Is your feature request related to a problem? Please describe.
The current business_status enum is missing a value: FUTURE_OPENING

Describe the solution you'd like
Add the value to the enum

Place Details API: Documentation error

For the Place Details API documentation, under the PlaceOpeningHours section, the description for the weekday_text field is copied from the description of the open_now text field.

image

The existing example for the weekday_text field shows the following JSON entry:

...
"weekday_text":
            [
              "Monday: 9:00 AM – 5:00 PM",
              "Tuesday: 9:00 AM – 5:00 PM",
              "Wednesday: 9:00 AM – 5:00 PM",
              "Thursday: 9:00 AM – 5:00 PM",
              "Friday: 9:00 AM – 5:00 PM",
              "Saturday: Closed",
              "Sunday: Closed",
            ],
...

I suggest a new description for the weekday_text field as follows:

An array of strings describing in human-readable text the weekly opening hours of the place.

This is just a suggestion. I'm not confident that it is accurate, and it could use some further clarification from someone who knows what the weekday_text field is supposed to be.

Thanks!

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.