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

Prepare release v2.2.0 #2411

Merged
merged 2 commits into from
Apr 19, 2018
Merged

Prepare release v2.2.0 #2411

merged 2 commits into from
Apr 19, 2018

Conversation

giladgray
Copy link
Contributor

@giladgray giladgray commented Apr 19, 2018

🎆 Highlights: customize CSS namespace, percentage-based Slider, Blueprint TSLint rules!

General

@blueprintjs/core 2.2.0

@blueprintjs/table 2.1.0

@blueprintjs/tslint-config 1.2.0

  • ⭐️ add new lint rules to ease migration #2394 Add a new lint rule blueprint-classes-constants to enforce use of Classes.* constants instead of "pt-prefixed-strings". This rule is enabled by default.
    • Also added blueprint-icon-components rule to enforce JSX component or string literal usage for icon props. This rule is disabled by default and has little practical purpose until we ship individual components for the icons A way to only bundle icons you actually use #2193
  • removed file-header configuration as it mentioned Palantir

Documentation

@giladgray giladgray requested review from themadcreator and llorca and removed request for themadcreator April 19, 2018 23:06
Copy link
Contributor

@llorca llorca left a comment

Choose a reason for hiding this comment

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

went through docs examples, looking good 👍

do we want a PSA at the top of the release notes asking consumers to start actioning on 3.0 items? i.e. start converting all your .pt-* classes to Classes.*?

@giladgray
Copy link
Contributor Author

mm not yet, once we cut 3.0.0-beta.0

@giladgray giladgray merged commit 5a3fd9c into develop Apr 19, 2018
@giladgray giladgray deleted the release/2.2.0 branch April 19, 2018 23:15
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