Add YGLayoutGetBorder, counterpart of YGLayoutGetPadding

[arcanis]

Followup of #335, fix #326. This commit add the YGLayoutGetBorder(node, edge) function, which correctly takes RTL/LTR into account when resolving EDGE_START & EDGE_END.

[arcanis]

@emilsjolander Can you publish a release on npm once this PR is merged? Due to this repository being monolithic by design, the package cannot be used with npm and yarn without performing a manual clone :)

[emilsjolander]

@arcanis sure, I can do this later this week or early next week.

[facebook-github-bot]

@emilsjolander has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[emilsjolander]

@arcanis What should I do to publish this on npm? I'm new to that whole ecosystem.

[emilsjolander]

@arcanis Also could you have a look at the js tests failing on travis?

[arcanis]

I think the tests are failing because the javascript/build/Release/nbind.js file hasn't been regenerated after one of the breaking changes - I've just pulled the repo, rebuilt it, and everything passed (this theory is supported by the fact that the native module tests are passing, which makes sense because they are automatically rebuilt when running npm install).

As for publishing, first ensure you have an npm account (I'm not sure if fb requires projects to be published under an umbrella account) by running npm adduser - If you don't have one, it should create it automatically. Otherwise, it will log you in.

Publish the first release:

• Jump into the javascript directory
• Run npm run build:all
• Run npm publish

Publish future releases:

• Jump into the javascript directory
• Run npm run build:all
• Run npm version <major/minor/patch> (will respectively bump major/minor/patch version number)
• Run npm publish

If you want, I can publish the initial release then give you access to the package.

[emilsjolander]

@arcanis I can give it a try! thanks