-
Notifications
You must be signed in to change notification settings - Fork 124
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: dart-lang/dart_style
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 2.2.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: dart-lang/dart_style
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 2.2.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 9 commits
- 16 files changed
- 2 contributors
Commits on Jan 12, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 7f5efd8 - Browse repository at this point
Copy the full SHA 7f5efd8View commit details
Commits on Jan 18, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 6f894c0 - Browse repository at this point
Copy the full SHA 6f894c0View commit details
Commits on Feb 11, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 4c15895 - Browse repository at this point
Copy the full SHA 4c15895View commit details
Commits on Feb 23, 2022
-
Formatting support for named arguments anywhere. (#1094)
* Formatting support for named arguments anywhere. I opted to add support for this while being minimally invasive to the existing style and formatting. All existing code which does not have any positional arguments after named ones retains its previous formatting. For new argument lists that use positional arguments after named ones, I try to mostly follow the existing style rules even though they can be fairly complex. In particular, it will be pretty aggressive about applying block-style formatting to function literals inside argument lists even with named args anywhere. I think that's important to support the main use case I know of for the feature which is trailing positional closures like: function(named: 1, another: 2, () { block... }); In argument lists using named args anywhere that don't have block functions, it treats all arguments like named ones. That provides nice simple formatting like: function( argument1, named: argument2, argument3, another: argument4); I think that does a good job of highlighting which arguments are named, which is what we want. Fix #1072. * Rewrite doc comments.
Configuration menu - View commit details
-
Copy full SHA for 68eab57 - Browse repository at this point
Copy the full SHA 68eab57View commit details -
Merge branch 'aa-use-internal-api' of https://github.com/scheglov/dar…
…t_style into scheglov-aa-use-internal-api
Configuration menu - View commit details
-
Copy full SHA for c461883 - Browse repository at this point
Copy the full SHA c461883View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4de83d3 - Browse repository at this point
Copy the full SHA 4de83d3View commit details
Commits on Mar 3, 2022
-
Format enhanced enums. (#1096)
* Format enhanced enums. Fix #1075. * Include constructor names in enum values. * Migrate off deprecated analyzer APIs.
Configuration menu - View commit details
-
Copy full SHA for c8ed552 - Browse repository at this point
Copy the full SHA c8ed552View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7adb2db - Browse repository at this point
Copy the full SHA 7adb2dbView commit details -
Configuration menu - View commit details
-
Copy full SHA for d7b7353 - Browse repository at this point
Copy the full SHA d7b7353View commit details
There are no files selected for viewing