greenkeeper[bot] commented 7 years ago

Version 1.7.0 of prettier just got published.

Branch	Build failing 🚨
Dependency	prettier
Current Version	1.6.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

prettier is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.com/AmpersandHQ/magepack-sdk/builds/54595394?utm_source=github_status&utm_medium=notification)

Release Notes

1.7.0: JSX tweaks, Pragma, TypeScript and CSS fixes

This release features some bugfixes and tweaks around JSX, TypeScript, CSS, and JavaScript formatting, as well as a couple new features.

Highlights

JSX Changes

We received a lot of community feedback about the changes we made to JSX formatting in the 1.6.0 release, and have made changes to bring formatting closer to community standards and expectations.

In 1.6.0, we added a second style for ternaries (conditional expressions, a ? b : c), based on a format popular in the community where parentheses are used to demarcate JSX content:

const DinnerOptions = ({ willEatMeat, willEatEggs, willEatVegetables }) => (
  <div>
    <div>Let's get some dinner...</div>
    {willEatMeat ? (
      <FullMenu />
    ) : willEatEggs ? (
      <VegetarianMenu />
    ) : willEatVegetables ? (
      <VeganMenu />
    ) : (
      <BackupMenu />
    )}
  </div>
);

Before this was added, prettier only formatted ternaries with one consistent style:

willEatMeat
  ? "Full Menu"
  : willEatEggs
    ? "Vegetarian Menu"
    : willEatVegetables ? "Vegan Menu" : "Backup Menu";

In 1.6.0, we used the following heuristic to decide when to use the new "JSX mode ternaries":

We should print a ternary using JSX mode if:
  * The ternary contains some JSX in it
  OR
  * The ternary appears inside of some JSX

However, this heuristic caused some unexpected formatting:

So, in 1.7.0, we have revised our heuristic to just be:

We should print a ternary using JSX mode if:
  * The ternary contains some JSX in it

We hope that this change will result in fewer surprising ternaries.

A big thanks goes out to @duailibe who implemented this change in addition to several other JSX-related formatting issues that were reported.

CSS Letter Case Consistency

We spent some time this release polishing our CSS formatting, and as part of that, @lydell did some work to normalize letter case.

So now, almost everything in CSS will print using lower case.

/* Before */
DIV.Foo {
  HEIGHT: 12PX;
}

/* After */
div.Foo {
  height: 12px;
}

Don't worry, though – Prettier won't touch your $scss-variables, @less-variables, or FunctionNames(). Preprocess on!

Pragma Support

There is a new option called --require-pragma (requirePragma via the API) which will change prettier's behavior so that it only reformats a file if it has a special "pragma" comment at the top of it, that looks like this:

/**
 * @prettier
 */

or

/**
 * @format
 */

This was @ajhyndman's idea and it was implemented by @wbinnssmith.

Other Changes

TypeScript

There was a bug in Prettier 1.6.1 where an error would be thrown while parsing any TypeScript using the never type, for example:

Observable.empty<never>();

Also, Prettier 1.6.1 was incorrectly removing the declare keyword from enum declarations in *.d.ts files:

// In
declare const enum Foo {}

// Out
const enum Foo {}

Both of these issues have been fixed. Thanks to @JamesHenry and @existentialism for these fixes which support our TypeScript community!

Configuration

Configurable Config Precedence

There is a new CLI option --config-precedence which configures how prettier should prioritize config sources. Valid values are:

cli-override (default) - CLI options take precedence over config file

file-override - Config file take precedence over CLI options

prefer-file - If a config file is found will evaluate it and ignore other CLI options. If no config file is found CLI options will evaluate as normal.

This option adds support to editor integrations where users define their default configuration but want to respect project specific configuration.

`prettier.resolveConfig.sync`

Previously, there was no way via the API to resolve configuration for a source file synchronously. Thanks to some new additions to cosmiconfig by @sudo-suhas, @ikatyang was able to add support for this to the prettier API.

PRs merged in this release

Issues resolved in this release

Document missing CLI options reported by @levithomason
Formatting of Spread Properties differs between Babylon and TypeScript reported by @mariusschulz
Removal of the declare modifier from enum reported by @mariusschulz
Decimal formatting doesn't get all decimals in a rule. reported by @itsgreggreg
Use resolveConfigFile.sync in the CLI reported by @azz
CSS: Normalize case (lower vs upper) on stuff reported by @lydell
Dynamic import with webpackChunkName comment fails reported by @pbomb
Typescript: never as type parameter causes error: unknown type: undefined reported by @hccampos
commented object values reported by @sylvainbaronnet
Configuring pre-commit for jsx, Typescript, tsx reported by @reywright
JSX ternaries include parens reported by @jasonLaster
Chained Short Circuit Conditionals in JSX reported by @brycehill
Support @prettier pragma comment reported by @ajhyndman
No indentation after breaking return statement reported by @jwbay
Support graphql() fn and so make 2nd arg prettier reported by @brikou
prettierignore: cannot use absolute filename reported by @ambar
Weird Javascript format reported by @maxime1992

Thank you to everyone who contributed to this release, be it through issue creation, code contribution, code review, or general commenting and feedback. Prettier is a community-run project and is able to continue to exist thanks to people like you. Thank you!

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 7 years ago

After pinning to 1.6.1 your tests are passing again. Downgrade this dependency 📌.

greenkeeper[bot] commented 7 years ago

Version 1.7.1 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

greenkeeper[bot] commented 7 years ago

Version 1.7.2 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

greenkeeper[bot] commented 7 years ago

Version 1.7.3 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

greenkeeper[bot] commented 7 years ago