The second annual Github Universe kicks off this Wednesday, September 14th in San Francisco. Universe is ‘the event for people building the future of software’ and will bring together 50+ speakers and 1,400 attendees from all over the world.The attendees are intentionally a mix of developers, technical leads and business leaders, which makes it a great place to be a developer advocate. Because the people who make the decisions that impact developers’ lives will be right here. Developer advocacy isn’t just about getting people to use your product, it’s about speaking up for all developers. CEOs, CTOs, and founders are coming to Universe because they want to hear this message—they want to know how to create the environments that developers thrive in. It’s our job to tell them.Handy links to tickets, map, schedule, speakers, sessions, afterparty, FAQ and @GithubUniverse.There are three must-haves for developers: trust, transparency, and community. Each value is essential to getting a quality job done day in and day out.

This year’s Github Universe program is packed with talks related to these values and I’ve done my best to highlight the ones that I’m most excited about. The guide is in chronological order.Octo-art from Universe 2015It is Saturday evening and it’s raining a lot in Ireland. So I decided to spend some time on Twitter looking for interesting TypeScript news. Over the last year I’ve been using the @DubTypeScript account to share TypeScript news. This is the official account of the Dublin TypeScript Meetup which is based in Dublin (Ireland) and is organized by myself. I was searching for interesting tweets when I found the following one: When I saw this tweet I was automatically thrilled because it is AWESOME when you find an opportunity to help the community like this. I really think it is sad that only a small percentage of all the software engineers out there contribute to open source. Contributing to open source is not easy for newcomers but I have seen a lot of initiatives to try to improve this over the past year.

Initiatives among which I would like to highlight the Hoodie efforts: And the “Your First PR” initiative: Your First PR helps you get started contributing to Open Source by showcasing great starter issues on Github and elsewhere. detroit lions superman hoodie- Your First PRelvine hoodie You may not believe me until you try it yourself but working on open source will make you a happier person. hoodie damen schnittmuster kostenlosYou might be working on an awesome project at work, in an amazing company with an amazing salary but nothing will fulfil you as much as helping others. naketano side zip grey hoodie

Helping others will give you a sense of purpose that no salary or pension will ever be able to give you. Working on open source has also helped me a lot in my professional career. ziener hoodieIt has allowed me to gain access to amazing opportunities like writing a technical book.north face men's flyweight hoodie jacket Or having the honor of being awarded with the Microsoft Most Valuable Professional (MVP) award:costco fleece hoodie In summary, contributing to open source will not only make you a happier person. It will also help you to become a better professional. In this article I’m going to explain how to create type definitions for an open source npm module. Please note that I’m assuming that you are familiar with TypeScript, Git and npm but you don’t need to be familiar with GitHub or React.

To create our own type definitions, we need to see the source code of the npm module for which we are trying to create type definitions. In this post we are working on the type definitions for the react-side-effect npm module. , you will be able to find a link to its GitHub repository on the right-hand side of the page: Follow the link to GitHub and try to find the package.json file using the file explorer. We then need find the main field in the package.json file: In 99% percent of the libraries, the main file is the /src/index.js file but, if that is not the case, the package.json file can help you to identify the main file. Head to the main file to see its source code. In this case, the main file can be found here. Wait a second, I just noticed something. This source code was created by Dan Abramov! This means that we are about to be able to learn from the source code one of the most popular software developers within the React and the JavaScript community.

This is an example of the kind of amazing opportunities that you will encounter if you work on open source. You will be able to learn from some of the best software engineers in the world and even get to know them for free! Once you find the source code, the first thing that we need to do, is to identify if this library was created using ES5 or ES6. We can usually identify the version of JavaScript being used by looking at the module imports. Then try identify which modules are imported (dependencies) and which elements are exported (public interface): It looks like this module depends on 2 other modules: When I search for the ExecutionEnvironment and shallowEqual variables in the source code, I can see that ExecutionEnvironment and shallowEqual are used internally and are not exported by react-side-effect. The module exports a function named withSideEffect, which the function takes 3 arguments named: The library is written in JavaScript so we don’t know the types of these 3 arguments.

At this point we can start creating our type definition file: I can also see that the withSideEffect function returns another function named wrap, which takes an argument named WrappedComponent. Once more we don’t know the type of this argument but by looking at its name and a typeof check we can guess that it is a React Component. The Warp function returns a React component named SideEffect. The last thing that we need to find out is the types of the arguments. This is the most complicated part. In this case I’m lucky because I’m familiar with React and the library is well documented. The handleStateChangeOnClient and mapStateOnServer arguments are functions that expect an object state as its only argument. Because I’m familiar with React I know that the state can take any from so I used the type any. Later I noticed that reducePropsToState actually takes an array as argument: At this point I updated the type definitions: Note that I have used export = because that is what I can see in the library’s source code.

Sometimes you will see export default x or export { x } you need to ensure that your type definitions file use the same kind of export that is used in the library. Now that we have the initial type definitions ready, we are going to try to add them to DefinitelyTyped. Once you are in the page you need to fork the repository (you will need to be logged in). You can fork the repository by clicking on the top right “fork” icon: After forking the repository, you will be redirected to the page of your fork. You need to find the HTTPS URL to clone your fork: Once you have the clone URL, you can clone the repository using the terminal or console of your operating system. When the repository has been cloned you need to move into the newly created folder: We are going to add a new type definition file so we can say that we are going to work on a new feature. We are going to create a new branch: We need to install the dependencies of this project: We can then create a new folder:

A new file for our type definitions: And a new file for the test of the type definitions: We can copy our initial type definitions into the react-side-effect.d.ts file that we just created. I copied it and added some comments required by DefinitelyTyped: To create the test, I just to copied one of the examples from the react-side-effect documentation. The example is written in JavaScript but can be migrated to TypeScript with ease: If we search in the DefinitelyTyped repository documents, we will be able to find the instructions to test our changes before sending a pull request: When I executed the tests I encountered two issues:Module ‘“react-side-effect”’ resolves to a non-module entity and cannot be imported using this construct. I was able to fix it adding a namespace. I found the solution after a quick search online: The second problem was that:Argument of type ‘typeof DocumentTitle’ is not assignable to parameter of type ‘Component’.

Property ‘setState’ is missing in type ‘typeof DocumentTitle’. I was able to fix this issue by going through the type definitions of other similar react libraries. I found the solution in the redux-forms type definitions: We are ready to send our changes to our fork. Let’s add the new folder to source control: Then check which files are ready to be committed: The files seem to be correct: We can now commit the changes: To finish, let’s push the changes to a new branch in our fork: If you head to the page of your fork on GitHub you will see a notice box which allows you to create a pull request (PR) for your changes: After creating the PR a the DefinitelyTyped continuous integration process will be triggered. The CI process will run the tests just like you have done in your local machine so it should be fine. This time the CI process has been successful ?? If your PR fails during the CI process, you will need to check the Travis CI logs.