Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/api extractor #32

Merged
merged 9 commits into from
Feb 12, 2019
Merged

Feature/api extractor #32

merged 9 commits into from
Feb 12, 2019

Conversation

nvh
Copy link
Contributor

@nvh nvh commented Feb 11, 2019

This now generates:

  • api/framer-motion.api.ts

And:

  • dist/framer-motion.api.json
  • dist/framer-motion.d.ts
  • dist/tsdoc-metadata.json

@aron can you verify that this is what we actually need?

@nvh nvh requested review from aron and mattgperry February 11, 2019 15:08
This is generated into the dist folder now
Copy link
Contributor

@aron aron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, rolled up definition file is much nicer. I technically only need the framer-motion.api.json but the framer-motion.api.ts is quite nice to see the exported surface.

@@ -56,6 +56,7 @@
},
"dependencies": {
"@emotion/is-prop-valid": "^0.7.3",
"@microsoft/api-extractor": "^7",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets tag this at 7.0.13 to ensure the output is the same as Library.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But that should be in the yarn.lock, right? I'll make sure that will say 7.0.13, because I think it's at 17 now

scrollYProgress: import(".").MotionValue<number>
}

// (No @packageDocumentation comment for this package)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this everything? Feels a little incomplete...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, this was everything api-extractor was complaining about, but I will double check

@mattgperry mattgperry merged commit 2ad0a66 into master Feb 12, 2019
@mattgperry mattgperry deleted the feature/api-extractor branch February 12, 2019 09:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants