Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: remove deprecated badge fixed values #4742

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rubencarvalho
Copy link
Collaborator

Description

Removed the sp-badge non-logical fixed property values along with all associated references and dependencies.

Related issue(s)

Motivation and context

For the upcoming 1.0.0 release of Spectrum Web Components, we will remove the deprecated components and features.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (minor updates related to the tooling or maintenance of the repository, does not impact compiled assets)

Checklist

  • I have signed the Adobe Open Source CLA.
  • My code follows the code style of this project.
  • If my change required a change to the documentation, I have updated the documentation in this pull request.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • I have reviewed at the Accessibility Practices for this feature, see: Aria Practices

Best practices

This repository uses conventional commit syntax for each commit message; note that the GitHub UI does not use this by default so be cautious when accepting suggested changes. Avoid the "Update branch" button on the pull request and opt instead for rebasing your branch against main.

@rubencarvalho rubencarvalho marked this pull request as ready for review September 11, 2024 12:57
@rubencarvalho rubencarvalho requested a review from a team as a code owner September 11, 2024 12:57
Copy link

Branch preview

Visual regression test results

When a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:

Copy link

Lighthouse scores

Category Latest (report) Main (report) Branch (report)
Performance 0.99 0.99 0.99
Accessibility 1 1 1
Best Practices 1 1 1
SEO 1 0.92 0.92
PWA 1 1 1
What is this?

Lighthouse scores comparing the documentation site built from the PR ("Branch") to that of the production documentation site ("Latest") and the build currently on main ("Main"). Higher scores are better, but note that the SEO scores on Netlify URLs are artifically constrained to 0.92.

Transfer Size

Category Latest Main Branch
Total 225.789 kB 214.33 kB 🏆 214.534 kB
Scripts 55.29 kB 49.755 kB 🏆 49.958 kB
Stylesheet 34.731 kB 30.161 kB 30.135 kB 🏆
Document 6.191 kB 5.436 kB 5.434 kB 🏆
Font 126.78 kB 126.605 kB 🏆 126.632 kB

Request Count

Category Latest Main Branch
Total 52 52 52
Scripts 41 41 41
Stylesheet 5 5 5
Document 1 1 1
Font 2 2 2

Copy link

Tachometer results

Chrome

badge permalink

basic-test

Version Bytes Avg Time vs remote vs branch
npm latest 412 kB 23.39ms - 24.07ms - unsure 🔍
-6% - +0%
-1.43ms - +0.03ms
branch 389 kB 23.79ms - 25.08ms unsure 🔍
-0% - +6%
-0.03ms - +1.43ms
-
Firefox

badge permalink

basic-test

Version Bytes Avg Time vs remote vs branch
npm latest 412 kB 48.30ms - 51.58ms - unsure 🔍
-10% - +0%
-5.06ms - +0.14ms
branch 389 kB 50.38ms - 54.42ms unsure 🔍
-0% - +10%
-0.14ms - +5.06ms
-

@coveralls
Copy link
Collaborator

Pull Request Test Coverage Report for Build 10812123757

Details

  • 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 98.205%

Totals Coverage Status
Change from base Build 10808456663: 0.0%
Covered Lines: 32500
Relevant Lines: 32931

💛 - Coveralls

@rubencarvalho rubencarvalho marked this pull request as draft September 24, 2024 11:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants