feat(selenium-migration): rename Selenium.Axe to Deque.AxeCore.Selenium #28
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates all references to the
Selenium.Axe
project naming to instead useDeque.AxeCore.Selenium
naming/layout. Specifically:Selenium.Axe
and into flattersrc
andtest
directories, similar to the layout used for the commons package in feat(commons): set up empty commons projects #27Selenium.Axe
toDeque.AxeCore.Selenium
.csproj
files' names and contents to match the new naming.gitignore
into the root-level oneOut of scope:
/packages/selenium/.github
directory in place for now; we'll migrate the existing contents out of it separately as part of Create/Configure CI pipeline #4 (for the workflows) and [Common] Set up repo-level doc files #7 (for the issue/PR templates)Recommend that reviewers verify that:
dotnet build
from the new/packages/selenium/src
directory succeeds and produces anupkg
in the expected layoutdotnet test
from the new/packages/selenium/test
directory runs and passes all the original tests (note: you will need both a .NET Core 3.1 SDK and a .NET 6 SDK installed)Completes #11