Skip to content

Commit

Permalink
Update master -> main in docs (#2524)
Browse files Browse the repository at this point in the history
* Remove bootstrap js

* Update master to main references.
  • Loading branch information
nojaf authored Sep 21, 2022
1 parent 11c2a86 commit dc8b277
Show file tree
Hide file tree
Showing 94 changed files with 30 additions and 23,342 deletions.
4 changes: 2 additions & 2 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,9 @@ assignees: ''
Go to https://fsprojects.github.io/fantomas-tools/#/fantomas/preview and reproduce your problem there.
Use the `create issue` link at the bottom, this will generate a report with everything we need to investigate your problem.

![Fantomas online tool](https://github.com/fsprojects/fantomas/blob/master/docs/fantomas-tools.png)
![Fantomas online tool](https://github.com/fsprojects/fantomas/blob/main/docs/fantomas-tools.png)

Try and reproduce your problem against the `preview` version of the tool, this is linked to the master branch of the project.
Try and reproduce your problem against the `preview` version of the tool, this is linked to the main branch of the project.

In case you wish to report another problem, continue writing this current issue.
Please review the [Contribution Guidelines](../../CONTRIBUTING.md).
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Related suggestions: (put links to related suggestions here)
## Affidavit (please submit!)

Please tick this by placing a cross in the box:
* [ ] I have read the [Contribution Guidelines](https://github.com/fsprojects/fantomas/blob/master/CONTRIBUTING.md).
* [ ] I have read the [Contribution Guidelines](https://github.com/fsprojects/fantomas/blob/main/CONTRIBUTING.md).
* [ ] I have [searched both open and closed suggestions on this site](https://github.com/fsprojects/fantomas/issues) and believe this is not a duplicate

Please tick all that apply:
Expand Down
2 changes: 1 addition & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -1053,7 +1053,7 @@
### Changed
* Use FCS 33.0.0. [pull/568](https://github.com/fsprojects/fantomas/pull/568)
* Use dotnet tools [pull/558](https://github.com/fsprojects/fantomas/pull/558)
* Add `--maxIfThenElseShortWidth` option, see [documentation](https://github.com/fsprojects/fantomas/blob/master/docs/Documentation.md)
* Add `--maxIfThenElseShortWidth` option, see [documentation](https://github.com/fsprojects/fantomas/blob/main/docs/Documentation.md)

## [3.0.0] - 2019-10-11

Expand Down
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -89,14 +89,14 @@ Use a helper function like `sepNlnConsideringTriviaContentBeforeForMainNode` ins

### ASTContext

In [CodePrinter.fs](https://github.com/fsprojects/fantomas/blob/master/src/Fantomas/CodePrinter.fs) the ASTContext record is used to indicate context aware information. This usually is an escape hatch and should be avoided at all times.
In [CodePrinter.fs](https://github.com/fsprojects/fantomas/blob/main/src/Fantomas/CodePrinter.fs) the ASTContext record is used to indicate context aware information. This usually is an escape hatch and should be avoided at all times.
The key issue is that flags of the ASTContext are usually not cleaned up after they served their purpose.
Leading to very strange situations and unexpected behavior.

# Bug reports

We prefer that all bugs are created using our online tool: https://fsprojects.github.io/fantomas-tools/ <br />
Here we can easily report bugs against the code of the latest master branch.
Here we can easily report bugs against the code of the latest main branch.
The tool generates a report with all the technical information that is necessary to reproduce the bug in a unit test.

Please try and make the bug report as small as possible. Isolate the part of your code that is causing the bug.
Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
Fantomas
========

![Fantomas logo](https://raw.githubusercontent.com/fsprojects/fantomas/master/fantomas_logo.png)
![Fantomas logo](https://raw.githubusercontent.com/fsprojects/fantomas/main/fantomas_logo.png)

![GitHub Workflow Status (event)](https://img.shields.io/github/workflow/status/fsprojects/fantomas/Build%20master?event=push&label=Build%20master&style=flat-square)
![GitHub Workflow Status (event)](https://img.shields.io/github/workflow/status/fsprojects/fantomas/Build%20main?event=push&label=Build%20main&style=flat-square)
[![Discord](https://img.shields.io/discord/940511234179096586?label=Fantomas%20Discord&style=flat-square)](https://discord.gg/D5QXvQrBVa)
[![Nuget (with prereleases)](https://img.shields.io/nuget/vpre/fantomas?style=flat-square)](https://www.nuget.org/packages/fantomas/absoluteLatest)

Expand Down
2 changes: 1 addition & 1 deletion docs-old/Documentation.md
Original file line number Diff line number Diff line change
Expand Up @@ -1020,7 +1020,7 @@ let main argv =

Surround **nested** multi-line expressions with blank lines.
Existing blank lines are always preserved (via trivia), with exception when [fsharp_keep_max_number_of_blank_lines](#fsharp_keep_max_number_of_blank_lines) is used.
Top level expressions will always follow the [2020 blank lines revision](https://github.com/fsprojects/fantomas/blob/master/docs/FormattingConventions.md#2020-revision) principle.
Top level expressions will always follow the [2020 blank lines revision](https://github.com/fsprojects/fantomas/blob/main/docs-old/FormattingConventions.md#2020-revision) principle.
Default = true.

`defaultConfig`
Expand Down
2 changes: 1 addition & 1 deletion docs-old/Fantomas-V.md
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ Performance was never the greatest motivator for these changes. But yes, a bette
A comparison was made on 30/04:

```
Master branch
main branch
| Method | Mean | Error | StdDev | Rank | Gen 0 | Gen 1 | Gen 2 | Allocated |
|------- |--------:|---------:|---------:|-----:|-----------:|-----------:|----------:|----------:|
Expand Down
2 changes: 1 addition & 1 deletion docs-old/ragnarok.md
Original file line number Diff line number Diff line change
Expand Up @@ -523,7 +523,7 @@ The impact will be huge in CodePrinter, there are numerous locations where some
I do believe that not placing the newline will not be the only thing that is required to make all these examples work.
Having an entirely new implementation for all the impacted nodes is also not recommended.

Some re-use might be possible on the record side by turning on [fsharp_multiline_block_brackets_on_same_column](https://github.com/fsprojects/fantomas/blob/master/docs/Documentation.md#fsharp_multiline_block_brackets_on_same_column).
Some re-use might be possible on the record side by turning on [fsharp_multiline_block_brackets_on_same_column](https://github.com/fsprojects/fantomas/blob/main/docs-old/Documentation.md#fsharp_multiline_block_brackets_on_same_column).
However, by doing this, a new precedent will be introduced. Two settings need to be combined in order for a valid code to be outputted.
This is unseen for the tool.

Expand Down
19 changes: 0 additions & 19 deletions docs/.style/bootstrap/js/index.esm.js

This file was deleted.

34 changes: 0 additions & 34 deletions docs/.style/bootstrap/js/index.umd.js

This file was deleted.

87 changes: 0 additions & 87 deletions docs/.style/bootstrap/js/src/alert.js

This file was deleted.

85 changes: 0 additions & 85 deletions docs/.style/bootstrap/js/src/base-component.js

This file was deleted.

72 changes: 0 additions & 72 deletions docs/.style/bootstrap/js/src/button.js

This file was deleted.

Loading

0 comments on commit dc8b277

Please sign in to comment.