-
-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #12 from AngleSharp/devel
0.15.0 release
- Loading branch information
Showing
17 changed files
with
120 additions
and
125 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -26,47 +26,50 @@ Discussion of issues should be placed transparently in the issue tracker here on | |
|
||
* [AngleSharp.Core](https://github.com/AngleSharp/AngleSharp/issues/) | ||
* [AngleSharp.Css](https://github.com/AngleSharp/AngleSharp.Css/issues/) | ||
* [AngleSharp.Diffing](https://github.com/AngleSharp/AngleSharp.Diffing/issues/) | ||
* [AngleSharp.Io](https://github.com/AngleSharp/AngleSharp.Io/issues/) | ||
* [AngleSharp.Js](https://github.com/AngleSharp/AngleSharp.Js/issues/) | ||
* [AngleSharp.Xml](https://github.com/AngleSharp/AngleSharp.Xml/issues/) | ||
* [AngleSharp.XPath](https://github.com/AngleSharp/AngleSharp.XPath/issues/) | ||
* [AngleSharp.Wasm](https://github.com/AngleSharp/AngleSharp.Wasm/issues/) | ||
|
||
### Modifying the code | ||
|
||
AngleSharp and its libraries uses features from the latest versions of C# (e.g., C# 7). You will therefore need a C# compiler that is up for the job. | ||
|
||
1. Fork and clone the repo. | ||
2. First try to build the AngleSharp.Core libray and see if you get the tests running. | ||
2. First try to build the AngleSharp.Core library and see if you get the tests running. | ||
3. You will be required to resolve some dependencies via NuGet. | ||
|
||
AngleSharp itself does not have dependencies, however, the tests are dependent on NUnit. | ||
|
||
The build system of AngleSharp uses Cake. A bootstrap script (build.ps1 for Windows or build.sh for *nix systems) is included. Note, that at the moment AngleSharp may require NuGet 3.5, which looks for MSBuild pre-15, i.e., before Visual Studio 2017 on Windows systems. We aim to drop this requirement enitirely soon. | ||
The build system of AngleSharp uses Cake. A bootstrap script (build.ps1 for Windows or build.sh for *nix systems) is included. Note, that at the moment AngleSharp may require NuGet 3.5, which looks for MSBuild pre-15, i.e., before Visual Studio 2017 on Windows systems. We aim to drop this requirement entirely soon. | ||
|
||
### Code Conventions | ||
|
||
Most parts in the AngleSharp project are fairly straight forward. Among these are: | ||
|
||
- Always use statement blocks for control statements, e.g., in a for-loop, if-condition, ... | ||
- You may use a simple (throw) statement in case of enforcing contracts on argument | ||
- Be explicit about modifiers (some files follow an older convention of the code base, but we settled on the explicit style) | ||
* Always use statement blocks for control statements, e.g., in a for-loop, if-condition, ... | ||
* You may use a simple (throw) statement in case of enforcing contracts on argument | ||
* Be explicit about modifiers (some files follow an older convention of the code base, but we settled on the explicit style) | ||
|
||
There are a couple of rules, which are definitely not standard, but highly recommended for consistency and readability: | ||
|
||
- AngleSharp uses the RHS convention, where types are always put on the right hand side if possible, i.e., preferring `var` under all circumstances | ||
- A single empty line between two non-simple statements (e.g., for-loop and if-condition) should be inserted | ||
- Types are preferred to keywords (`String` instead of `string` or `Int32` instead of `int`) | ||
- `using` statements must be inside the namespace declaration | ||
* AngleSharp uses the RHS convention, where types are always put on the right hand side if possible, i.e., preferring `var` under all circumstances | ||
* A single empty line between two non-simple statements (e.g., for-loop and if-condition) should be inserted | ||
* Types are preferred to keywords (`String` instead of `string` or `Int32` instead of `int`) | ||
* `using` statements must be inside the namespace declaration | ||
|
||
### Development Workflow | ||
|
||
1. If no issue already exists for the work you'll be doing, create one to document the problem(s) being solved and self-assign. | ||
2. Otherwise please let us know that you are working on the problem. Regular status updates (e.g. "still in progress", "no time anymore", "practically done", "pull request issued") are highly welcome. | ||
2. Create a new branch—please don't work in the `master` branch directly. It is reserved for releases. We recommend naming the branch to match the issue being addressed (`feature/#777` or `issue-777`). | ||
3. Add failing tests for the change you want to make. Tests are crucial and should be taken from W3C (or other specification). | ||
4. Fix stuff. Always go from edge case to edge case. | ||
5. All tests should pass now. Also your new implementation should not break existing tests. | ||
6. Update the documentation to reflect any changes. (or document such changes in the original issue) | ||
7. Push to your fork or push your issue-specific branch to the main repository, then submit a pull request against `devel`. | ||
3. Create a new branch—please don't work in the `master` branch directly. It is reserved for releases. We recommend naming the branch to match the issue being addressed (`feature/#777` or `issue-777`). | ||
4. Add failing tests for the change you want to make. Tests are crucial and should be taken from W3C (or other specification). | ||
5. Fix stuff. Always go from edge case to edge case. | ||
6. All tests should pass now. Also your new implementation should not break existing tests. | ||
7. Update the documentation to reflect any changes. (or document such changes in the original issue) | ||
8. Push to your fork or push your issue-specific branch to the main repository, then submit a pull request against `devel`. | ||
|
||
Just to illustrate the git workflow for AngleSharp a little bit more we've added the following graphs. | ||
|
||
|
@@ -76,19 +79,19 @@ Here we now created a new branch called `devel`. This is the development branch. | |
|
||
Now active work is supposed to be done. Therefore a new branch should be created. Let's create one: | ||
|
||
``` | ||
```sh | ||
git checkout -b feature/#777 | ||
``` | ||
|
||
There may be many of these feature branches. Most of them are also pushed to the server for discussion or synchronization. | ||
|
||
``` | ||
```sh | ||
git push -u origin feature/#777 | ||
``` | ||
|
||
Now feature branches may be closed when they are done. Here we simply merge with the feature branch(es). For instance the following command takes the `feature/#777` branch from the server and merges it with the `devel` branch. | ||
|
||
``` | ||
```sh | ||
git checkout devel | ||
git pull | ||
git pull origin feature/#777 | ||
|
@@ -97,7 +100,7 @@ git push | |
|
||
Finally, we may have all the features that are needed to release a new version of AngleSharp. Here we tag the release. For instance for the 1.0 release we use `v1.0`. | ||
|
||
``` | ||
```sh | ||
git checkout master | ||
git merge devel | ||
git tag v1.0 | ||
|
@@ -109,12 +112,11 @@ git tag v1.0 | |
|
||
The following files should not be edited directly in the current repository, but rather in the `AngleSharp.GitBase` repository. They are then synced via `git pull` from a different remote. | ||
|
||
``` | ||
```plaintext | ||
.editorconfig | ||
.gitignore | ||
.gitattributes | ||
.github/* | ||
appveyor.yml | ||
build.ps1 | ||
build.sh | ||
tools/anglesharp.cake | ||
|
@@ -124,7 +126,7 @@ LICENSE | |
|
||
To sync manually: | ||
|
||
``` | ||
```sh | ||
git remote add gitbase [email protected]:AngleSharp/AngleSharp.GitBase.git | ||
git pull gitbase master | ||
``` | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,4 @@ | ||
# These are supported funding model platforms | ||
|
||
github: [egil] # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2] | ||
#patreon: # Replace with a single Patreon username | ||
#open_collective: # Replace with a single Open Collective username | ||
#ko_fi: # Replace with a single Ko-fi username | ||
#tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel | ||
#community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry | ||
#liberapay: # Replace with a single Liberapay username | ||
#issuehunt: # Replace with a single IssueHunt username | ||
#otechie: # Replace with a single Otechie username | ||
#custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2'] | ||
github: [FlorianRappl,egil] | ||
custom: https://salt.bountysource.com/teams/anglesharp |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
name: CI | ||
|
||
on: [push, pull_request] | ||
|
||
env: | ||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
NUGET_API_KEY: ${{ secrets.NUGET_API_KEY }} | ||
|
||
jobs: | ||
linux: | ||
runs-on: ubuntu-latest | ||
|
||
steps: | ||
- uses: actions/checkout@v2 | ||
|
||
- name: Build | ||
run: ./build.sh | ||
|
||
windows: | ||
runs-on: windows-latest | ||
|
||
steps: | ||
- uses: actions/checkout@v2 | ||
|
||
- name: Build | ||
run: | | ||
if ($env:GITHUB_REF -eq "refs/heads/master") { | ||
.\build.ps1 -Target Publish | ||
} elseif ($env:GITHUB_REF -eq "refs/heads/devel") { | ||
.\build.ps1 -Target PrePublish | ||
} else { | ||
.\build.ps1 | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
using System.Runtime.CompilerServices; | ||
[assembly: InternalsVisibleTo("AngleSharp.Diffing.Tests, PublicKey=002400000480000094000000060200000024000052534131000400000100010001adf274fa2b375134e8e4558d606f1a0f96f5cd0c6b99970f7cce9887477209d7c29f814e2508d8bd2526e99e8cd273bd1158a3984f1ea74830ec5329a77c6ff201a15edeb8b36ab046abd1bce211fe8dbb076d7d806f46b15bfda44def04ead0669971e96c5f666c9eda677f28824fff7aa90d32929ed91d529a7a41699893")] |
Oops, something went wrong.