[YogaKit] Improved the objective-c and swift api #322
Reference in New Issue
Block a user
No description provided.
Delete Branch "improve-yogakit-api"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Compared to what was planned, I added the
overflow
value which seemed missing. I had to modify the implementation a bit for all values which are backed by aYGValue
, but we should probably enable the pixel dimensions in Objective-C and Swift somehow later.Just a few comments. Mostly this looks very good and I'm pretty confident we can merge this later today. Thanks!
@@ -0,0 +1,114 @@
/**
This import seems unused, could you remove it?
@@ -0,0 +1,380 @@
/**
UIView *view
This function seems unused. Could you remove it?
@@ -14,29 +14,29 @@
YG_EXTERN_C_BEGIN
Could we make this generate something short (less duplicated) ? Maybe by creating our own YG_ENUM macro which expands to one of the two alternatives.
Pulling this out into a separate file seems to not be needed for this PR. Could you revert this change?
I implemented all your suggestions 😄 Thanks 👍
We should change this to
strong
http://nshipster.com/associated-objects/
@emilsjolander has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
@@ -0,0 +93,4 @@
- (instancetype)initWithView:(UIView*)view
{
if ([super init]) {
Nit, we should be assigning this to
self
, i.e.self = [super init]
I know this isn't technically required, but I think it's good to keep the standard. More about that here: https://www.cocoawithlove.com/2009/04/what-does-it-mean-when-you-assign-super.html
@hartbit Don't worry about it. I'll fix this while mergin
Awesome job @hartbit!! I'm so excited to land this!
It looks like the import of this commit into react-native causes CI tests to fail. Can somebody help fix this ASAP?
https://travis-ci.org/facebook/react-native/builds/190054212
@ericvicenti looking now
@ericvicenti Found issue. Pushing fix within next few hours
@emilsjolander What was the problem?
0acb620159
Ah, of course!
Pull request closed