profile
viewpoint
Ben Hong bencodezen Cypress.io DC Metro Area http://www.bencodezen.io developer / psychologist / educator hybrid ∙ @vuejs core team ∙ @cypress-io dx engineer ∙ VueMastery instructor ∙ @googledevexpert

bahmutov/cypress-vue-unit-test 244

A little helper to unit test Vue components in the Cypress.io E2E test runner

1950Labs/vuejs.org 14

📄 The official documentation site for Vue.js.

bencodezen/bens-blog-boilerplate 4

An open-sourced opinionated blogging infrastructure that Ben uses to power his own blog

bencodezen/alexa-game-keeper 1

An Alexa skill to serve as a companion to game nights!

bencodezen/coffeeaddict 1

Simple coffee shop locator.

bencodezen/alexa-fact-skill 0

Experimentation with Alexa Fact Skill

bencodezen/alexa-go-quiz-skill 0

A quiz on Alexa about go/baduk/weiqi!

push eventbencodezen/vuepress-sandbox

Ben Hong

commit sha 634f1f0a1f02fafd593445181726c9f836579ab7

feature: setup project

view details

push time in 39 minutes

create barnchbencodezen/vuepress-sandbox

branch : master

created branch time in 41 minutes

created repositorybencodezen/vuepress-sandbox

created time in 41 minutes

push eventcypress-io/cypress-documentation

Ben Hong

commit sha fd0a9947f32557c09584cb1c9d6c13b3bdd8dad4

docs: centralize phrasing on retry attempts

view details

push time in 3 hours

pull request commentcypress-io/cypress-documentation

docs: 5.0.0 release docs test retries

@Bkucera @JessicaSachs changes applied and feedback taken!

bencodezen

comment created time in 3 hours

pull request commentcypress-io/cypress-documentation

docs: 5.0.0 release docs test retries

Need to update this section on 'Debugging flake' to recommend they try 'Test Retries' https://github.com/cypress-io/cypress-documentation/blob/5.0.0-release-docs-test-retries/source/guides/guides/debugging.md#L134:L134

Which section are you referring to @jennifer-shehane?

bencodezen

comment created time in 3 hours

Pull request review commentcypress-io/cypress-documentation

docs: 5.0.0 release docs test retries

+---+title: Test Retries+---++{% note info %}+# {% fa fa-graduation-cap %} What you'll learn++- What are test retries?+- Why is test retries important?

Good catch @CypressCecelia!

bencodezen

comment created time in 3 hours

push eventcypress-io/cypress-documentation

Ben Hong

commit sha 7c9ad7311407741cff5edbaed70cada81d347124

docs: fix grammatical plural

view details

push time in 3 hours

push eventcypress-io/cypress-documentation

Ben Hong

commit sha 28fd37483b0ce3eb6e1a3a5bebf2f0537d551e3b

docs: standardize reference to retry attempts

view details

push time in 3 hours

Pull request review commentcypress-io/cypress-documentation

docs: 5.0.0 release docs test retries

+---+title: Test Retries+---++{% note info %}+# {% fa fa-graduation-cap %} What you'll learn++- What are test retries?+- Why is test retries important?+- How to configure test retries+{% endnote %}++# Introduction++End-to-end (E2E) tests excel at testing complex systems. However, there are still behaviors that are hard to verify and make tests flaky (i.e., unreliable) and fail sometimes due to unpredictable conditions (eg., temporary outages in external dependencies, random network errors, etc.).  Some other common race conditions that could result in unreliable tests include:++- Animations+- API calls+- Test server / database availability+- Resource dependencies availability+- Network issues++With test retries, Cypress is able to retry failed tests to help reduce test flakiness and continuous integration (CI) build failures. By doing so, this will save your team valuable time and resources so you can focus on what matters most to you.++# How It Works++By default, tests will not retry when they fail. You will need to {% urlHash "enable test retries in your configuration" Configure-Test-Retries %} to use this feature.++When test retries is on, tests will automatically be retried up to X additional times based on your desired configuration. For example, if test retries is set to `2`, it will retry tests up to 2 additional times (for a total of 3 attempts) before potentially being marked as a failed test.++When each test is run again, the following {% url "hooks" writing-and-organizing-tests#Hooks %} will be re-run also:++- `beforeEach`+- `afterEach`++{% note warning %}+However, `before` and `after` hooks will not be run in next attempts.+{% endnote %}++**The following is a detailed step-by-step example of how test retries works:**++Assuming we have set test retries to `2` (for a total of 3 attempts), the following is how the tests would run.++1. A test runs for the first time. If the {% fa fa-check-circle green %} test passes, Cypress will move forward with any remaining tests as usual.++2. If the {% fa fa-times red %} test fails, Cypress will tell you that the first attempt failed and will to run the test a second time.++{% img /img/guides/test-retries/attempt-2-start.png %}++3. If the {% fa fa-check-circle green %} test passes after the second attempt, Cypress will continue with any remaining tests.++4. If the {% fa fa-times red %} test fails a second time, it will make the final third attempt to re-run the test.++{% img /img/guides/test-retries/attempt-3-start.png %}++5. If the {% fa fa-times red %} test fails a third time, Cypress will mark the test as failed and then move on to run any remaining tests.++{% img /img/guides/test-retries/attempt-3-fail.png %}++The following is a screen capture of what test retries looks like on the same failed test when run via {% url "`cypress run`" command-line#cypress-run %}.++{% img /img/guides/test-retries/cli-error-message.png %}++During {% url "`cypress open`" command-line#cypress-open %} you will be able to see the number of attempts made in the {% url "Command Log" test-runner#Command-Log %} and expand each attempt for review and debugging if desired.++{% video local /img/guides/test-retries/attempt-expand-collapse-time-travel.mp4 %}++# Configure Test Retries++## Global Configuration++If you want to change the number of attempts being made for all tests run for both `cypress run` and `cypress open`, you can configure this in your {% url "configuration file" command-line#cypress-open-config-file-lt-config-file-gt %} (`cypress.json` by default) by defining the `retries` property and giving it the desired number of retries.++```jsx+{+  "retries": 1+}+```++### Disable Test Retries++If you would like to disable test retries completely (the default configuration), you can use the global configuration to do so by setting `retries` to 0.++```jsx+{+  "retries": 0+}+```++### Configure specific retries for different modes++If you want to define different retry attempts for `cypress run` versus `cypress open`, you can pass the `retries` option an object with the following options:++- `runMode` allows you to define the number of test retries when running `cypress run`+- `openMode` allows you to define the number of test retries when running `cypress open`++```jsx+{+  "retries": {+    // Configure retries for `cypress run`+    // Default is 0+    "runMode": 2,+    // Configure retries for `cypress open`+    // Default is 0+    "openMode": 1+  }+}+```++## Custom Configurations++### Individual Test(s)++If you want a specific test to run a custom number of retries, you can set this by using the {% url "test's configuration" writing-and-organizing-tests#Test-Configuration %}.

Great point @Bkucera! Going to try and restructure this.

bencodezen

comment created time in 3 hours

push eventcypress-io/cypress-documentation

Ben Hong

commit sha e123836afad1cb93d935845bb9c6e4bc661b724e

docs: show custom screenshot name in action

view details

push time in 4 hours

Pull request review commentcypress-io/cypress-documentation

docs: 5.0.0 release docs test retries

+---+title: Test Retries+---++{% note info %}+# {% fa fa-graduation-cap %} What you'll learn++- What are test retries?+- Why is test retries important?+- How to configure test retries+{% endnote %}++# Introduction++End-to-end (E2E) tests excel at testing complex systems. However, there are still behaviors that are hard to verify and make tests flaky (i.e., unreliable) and fail sometimes due to unpredictable conditions (eg., temporary outages in external dependencies, random network errors, etc.).  Some other common race conditions that could result in unreliable tests include:++- Animations+- API calls+- Test server / database availability+- Resource dependencies availability+- Network issues++With test retries, Cypress is able to retry failed tests to help reduce test flakiness and continuous integration (CI) build failures. By doing so, this will save your team valuable time and resources so you can focus on what matters most to you.++# How It Works++By default, tests will not retry when they fail. You will need to {% urlHash "enable test retries in your configuration" Configure-Test-Retries %} to use this feature.++When test retries is on, tests will automatically be retried up to X additional times based on your desired configuration. For example, if test retries is set to `2`, it will retry tests up to 2 additional times (for a total of 3 attempts) before potentially being marked as a failed test.++When each test is run again, the following {% url "hooks" writing-and-organizing-tests#Hooks %} will be re-run also:++- `beforeEach`+- `afterEach`++{% note warning %}+However, `before` and `after` hooks will not be run in next attempts.+{% endnote %}++**The following is a detailed step-by-step example of how test retries works:**++Assuming we have set test retries to `2` (for a total of 3 attempts), the following is how the tests would run.++1. A test runs for the first time. If the {% fa fa-check-circle green %} test passes, Cypress will move forward with any remaining tests as usual.++2. If the {% fa fa-times red %} test fails, Cypress will tell you that the first attempt failed and will to run the test a second time.++{% img /img/guides/test-retries/attempt-2-start.png %}++3. If the {% fa fa-check-circle green %} test passes after the second attempt, Cypress will continue with any remaining tests.++4. If the {% fa fa-times red %} test fails a second time, it will make the final third attempt to re-run the test.++{% img /img/guides/test-retries/attempt-3-start.png %}++5. If the {% fa fa-times red %} test fails a third time, Cypress will mark the test as failed and then move on to run any remaining tests.++{% img /img/guides/test-retries/attempt-3-fail.png %}++The following is a screen capture of what test retries looks like on the same failed test when run via {% url "`cypress run`" command-line#cypress-run %}.++{% img /img/guides/test-retries/cli-error-message.png %}++During {% url "`cypress open`" command-line#cypress-open %} you will be able to see the number of attempts made in the {% url "Command Log" test-runner#Command-Log %} and expand each attempt for review and debugging if desired.++{% video local /img/guides/test-retries/attempt-expand-collapse-time-travel.mp4 %}++# Configure Test Retries++## Global Configuration++If you want to change the number of attempts being made for all tests run for both `cypress run` and `cypress open`, you can configure this in your {% url "configuration file" command-line#cypress-open-config-file-lt-config-file-gt %} (`cypress.json` by default) by defining the `retries` property and giving it the desired number of retries.++```jsx+{+  "retries": 1+}+```++### Disable Test Retries++If you would like to disable test retries completely (the default configuration), you can use the global configuration to do so by setting `retries` to 0.++```jsx+{+  "retries": 0+}+```++### Configure specific retries for different modes++If you want to define different retry attempts for `cypress run` versus `cypress open`, you can pass the `retries` option an object with the following options:++- `runMode` allows you to define the number of test retries when running `cypress run`+- `openMode` allows you to define the number of test retries when running `cypress open`++```jsx+{+  "retries": {+    // Configure retries for `cypress run`+    // Default is 0+    "runMode": 2,+    // Configure retries for `cypress open`+    // Default is 0+    "openMode": 1+  }+}+```++## Custom Configurations++### Individual Test(s)++If you want a specific test to run a custom number of retries, you can set this by using the {% url "test's configuration" writing-and-organizing-tests#Test-Configuration %}.++```jsx+// Customize retries for an individual test+describe('User sign-up and login', () => {+  // `it` test block with no custom configuration+  it('should redirect unauthenticated user to sign-in page', () => {+    // ...+  })++  // `it` test block with custom configuration+  it('allows user to login', {+    retries: {+      runMode: 2,+      openMode: 1+    }+  }, () => {+    // ...+  })+})+```++### Test Suite(s)++If you want a suite of tests to re-run a custom number of times, you can do this by setting the suite's configuration.++```jsx+// Customizing retries for a suite of tests+describe('User bank accounts', {+  retries: {+    runMode: 2,+    openMode: 1,+  }+}, () => {+  // Individual tests will be run normally+  it('allows a user to view their transactions, () => {+    // ...+  }++  it('allows a user to edit their transactions, () => {+    // ...+  }+})+```++You can find more information about custom configurations here: {% url "Test Configuration" configuration#Test-Configuration %}++# Screenshots++With test retries, Cypress will take a separate screenshot for each test attempt. These will be properly labeled with the attempt number appended at the end of each filename.++With the following test code, you would see the below screenshot filename when all 3 attempts fail:++```js+describe('User Login', () => {+  it('displays login errors', () => {+    cy.visit('/')+    cy.screenshot()+    // ...+  })+})+```++```js+// screenshot filename from cy.screenshot() on 1st attempt+'User Login -- displays login errors.png'+// screenshot filename on 1st failed attempt+'User Login -- displays login errors (failed).png'+// screenshot filename from cy.screenshot() on 2nd attempt+'User Login -- displays login errors (attempt 2).png'+// screenshot filename on 2nd failed attempt+'User Login -- displays login errors (failed) (attempt 2).png'+// screenshot filename from cy.screenshot() on 3rd attempt+'User Login -- displays login errors (attempt 3).png'+// screenshot filename on 3rd failed attempt+'User Login -- displays login errors (failed) (attempt 3).png'

This is an interesting point for sure. I think in this case, it would probably be nice to surface that user's have this ability to name their screenshots. Users who aren't used to doing this should be able to follow this given the simplicity of the example, so I think there is merit to @Bkucera's change.

bencodezen

comment created time in 4 hours

push eventcypress-io/cypress-documentation

Ben Hong

commit sha 5fa4c6e716393c98838d04ea26f22028b2bd7603

docs: add specific image name Co-authored-by: Ben Kucera <14625260+Bkucera@users.noreply.github.com>

view details

push time in 4 hours

push eventcypress-io/cypress-documentation

Ben Hong

commit sha 18b6a6121e75ca78000293d4beae2853a75b6397

docs: make phrasing more accurate Co-authored-by: Jessica Sachs <jess@jessicasachs.io>

view details

push time in 4 hours

push eventcypress-io/cypress-documentation

Ben Hong

commit sha 003b66fa3b5eccaa5cf4d1f330c12fd3366844fc

docs: clarify meaning Co-authored-by: Jessica Sachs <jess@jessicasachs.io>

view details

push time in 4 hours

push eventcypress-io/cypress-documentation

Ben Hong

commit sha 7ed0b1b27819df0207498e0893afda505a37c3f6

docs: remove strategies piece Co-authored-by: Jessica Sachs <jess@jessicasachs.io>

view details

push time in 4 hours

push eventcypress-io/cypress-documentation

Ben Hong

commit sha 8772ef1e1b15f877e2883ad4efc25a91b3ee84d0

docs: update screenshots for dashboard analytics

view details

Ben Hong

commit sha aa1fac575c8869dc3254e6e8b9f31c83be22b348

style: add new line

view details

Ben Hong

commit sha 18a49f141a9101d64e3046c7eaba35627647c0d9

docs: add screenshots in placeholders for test failures and slowest tests

view details

Ben Hong

commit sha d1156f8759a30dff39410ae23f52b09979946444

docs: update dashboard anaytics top failures and slowest tests

view details

Ben Hong

commit sha 09c74f1596010d918e483a25c6594cc65a5a04ae

docs: add test case history to runs

view details

Ben Hong

commit sha 16b0dab3676ab350c35fe910339169dc5f92ddbd

style: remove random new line

view details

Ben Hong

commit sha e18388ae2824339569a1838ecccba1c9896377dd

docs: remove unnecessary h1s

view details

Ben Hong

commit sha 212df4fe4d09c6deff8d2f821ac3f5fc84077c89

docs: update images without beta tags

view details

Ben Hong

commit sha a33f8386cfb770d583dfd9e2257de8c42558212d

docs: remove references to beta for dashboard analytics

view details

Ben Hong

commit sha 6d57da84ed0d5f0686799f69db2c9f242dcd69db

content: update dashboard content

view details

Ben Hong

commit sha 9cf615ee16aab85c6f50c7dd8b79a44aaa24a4ee

docs: fix description

view details

Ben Hong

commit sha cbce5a4bed92a09041f455cfda225e4058ee3c70

docs: add views by documentation

view details

Ben Hong

commit sha 1ef5cdc5f5004d63da3ed410f57d471a1858d0f4

docs: bump heading hierarchy

view details

Ben Hong

commit sha 2c3d1e081d1318260d2492e6fd9fbb1b10a58c38

docs: update test case history screenshot

view details

Ben Hong

commit sha 8a8ec233c4dcc97a7075b3cea5c3aa9247385606

docs: update test case history description

view details

Jeff Tucker

commit sha 18ef07d9f89341c400937de0428c470b9c8d2c0e

Copy tweaks

view details

Ben Hong

commit sha fa3d42f6834ca980c842d3de485f05a4e06fb1af

docs: fix grammar Co-authored-by: Jennifer Shehane <jennifer@cypress.io>

view details

Ben Hong

commit sha 64543379830ec73fb876d82be29403bdc16a4c94

docs: fix diction Co-authored-by: Jennifer Shehane <jennifer@cypress.io>

view details

Ben Hong

commit sha 91f45c3856e25dac1635d851f3d1a8dce00dc542

docs: remove content

view details

Ben Hong

commit sha d57e491d8332a2909f583e88ece8a6517d2525b4

docs: remove unnecessary verb

view details

push time in 7 hours

push eventcypress-io/cypress-documentation

Ben Hong

commit sha d57e491d8332a2909f583e88ece8a6517d2525b4

docs: remove unnecessary verb

view details

push time in 7 hours

Pull request review commentcypress-io/cypress-documentation

docs/dashboard test history updates

 Unique tests and number of spec files are computed respective of the filters sel {% imgTag /img/dashboard/analytics/dashboard-analytics-test-suite-size-table.png "Dashboard Analytics Test Suite Size Table Screenshot" %}  A table of results grouped by date for the time range filter is displayed with unique tests and spec files.++## Top failures++{% imgTag /img/dashboard/analytics/dashboard-analytics-top-failures.png "Dashboard Analytics Top Failures Screenshot" %}++This report shows the top failures in your test suite.++### Filters and Views++{% imgTag /img/dashboard/analytics/dashboard-analytics-top-failures-filters.png "Dashboard Analytics Top Failures Filters Screenshot" %}++Results can be seen through custom grouping by using the "View By" dropdown. It can be grouped by:++- Test Case+- Spec File+- Tag+- Branch++Results may also be filtered by:++- Branch+- Tag+- Time Range+- Run Group+- Committer+- Spec File+- Browser+- Cypress Version+- Operating System++### Results++{% imgTag /img/dashboard/analytics/dashboard-analytics-top-failures-graph.png "Dashboard Analytics Top Failures Graph Screenshot" %}++The number of tests by failure rate is displayed respective of the filters selected.++The results may be downloaded as a comma-separated values (CSV) file for further analysis.++This can be done via the download icon to the right of the filters.++### Key Performance Indicators++{% imgTag /img/dashboard/analytics/dashboard-analytics-top-failures-kpi.png "Dashboard Analytics Top Failures KPI Screenshot" %}++The main key performance indicators tracked are:++- Median failure rate+- Number of failures (measured by test cases)++{% imgTag /img/dashboard/analytics/dashboard-analytics-top-failures-table.png "Dashboard Analytics Top Failures Table Screenshot" %}++A table of results grouped by failure rate is displayed with spec files and total runs.++## Slowest tests++{% imgTag /img/dashboard/analytics/dashboard-analytics-slowest-tests.png "Dashboard Analytics Slowest Tests Screenshot" %}++This report shows the slowest tests in a test suite.++### Filters and Views++{% imgTag /img/dashboard/analytics/dashboard-analytics-slowest-tests-filters.png "Dashboard Analytics Slowest Tests Filters Screenshot" %}++Results can be seen through custom grouping by using the "View By" dropdown. It can be grouped by:++- Test Case+- Spec File+- Tag+- Branch++Results may also be filtered by:++- Branch+- Tag+- Time Range+- Status+- Run Group+- Committer+- Spec File+- Browser+- Cypress Version+- Operating System++### Results++{% imgTag /img/dashboard/analytics/dashboard-analytics-slowest-tests-graph.png "Dashboard Analytics Slowest Tests Graph Screenshot" %}++The slowest tests are displayed by duration of time.++The results may be downloaded as a comma-separated values (CSV) file for further analysis.+This can be done via the download icon to the right of the filters.++### Key Performance Indicators++{% imgTag /img/dashboard/analytics/dashboard-analytics-slowest-tests-kpi.png "Dashboard Analytics Slowest Tests KPI Screenshot" %}++The main key performance indicators tracked are:++- Median duration+- Total number of test cases++{% imgTag /img/dashboard/analytics/dashboard-analytics-slowest-tests-table.png "Dashboard Analytics Slowest Tests Table Screenshot" %}++A table of results grouped by median duration and provides total runs.
A table of results grouped by median duration and total runs.
bencodezen

comment created time in 7 hours

push eventcypress-io/cypress-documentation

Ben Hong

commit sha 91f45c3856e25dac1635d851f3d1a8dce00dc542

docs: remove content

view details

push time in 7 hours

Pull request review commentcypress-io/cypress-documentation

docs/dashboard test history updates

 Runs that have been canceled or are in an errored state can be archived from the   `https://dashboard.cypress.io/projects/{project ID}/runs/{run number}` - Click **{% fa fa-history %} Restore from archive**   {% imgTag /img/dashboard/restore-from-archive.png "restore-from-archive" %}++# Test Case History++{% imgTag /img/dashboard/runs/dashboard-runs-details-sidebar-test-case-history.png "Screenshot of the Test Case History panel" %}++When looking further into a test runs information, there is a new Test Case History panel. It matches test cases by spec and title and combines it with commit information to provide users insight to:++1. See the history of a test over its lifespan+1. View the diff of a single test case*+1. Jump directly to the commit+1. See what run number each test snapshot is associated with
bencodezen

comment created time in 7 hours

push eventcypress-io/cypress-documentation

Ben Hong

commit sha 64543379830ec73fb876d82be29403bdc16a4c94

docs: fix diction Co-authored-by: Jennifer Shehane <jennifer@cypress.io>

view details

push time in 7 hours

push eventcypress-io/cypress-documentation

Ben Hong

commit sha fa3d42f6834ca980c842d3de485f05a4e06fb1af

docs: fix grammar Co-authored-by: Jennifer Shehane <jennifer@cypress.io>

view details

push time in 7 hours

push eventVueDC/vuedc

Ben Hong

commit sha eaf6f0bb013d272d413d79e445b1e75b05438fef

content: add august 2020 cover image assets

view details

push time in 19 hours

create barnchvuejs/docs-next

branch : docs/add-oxford-comma-image-source

created branch time in 21 hours

push eventvuejs/docs-next

Ben Hong

commit sha 223eac0a090c4fb9754c4bc9b0e0155616235382

docs (#391): update provide inject in composition api with enhanced reactivity (#396) * docs: use maps example in provide inject composition * docs: update code sample to show object * docs (#391): enhance provide inject reactivity section * docs: update disclaimer for provide inject composition api * docs: fix imports * docs: remove unnecessary qualifier * docs: fix grammar in disclaimer * docs: integrate tip into content

view details

push time in a day

PR merged vuejs/docs-next

Reviewers
docs (#391): update provide inject in composition api with enhanced reactivity review-alert-box

The PR was originally supposed to just be a small change regarding readonly, but then I came up with this scenario to explain provide / inject that I thought would be helpful.

Netlify Preview

Feedback welcome as always!

Closes #391

+230 -71

1 comment

1 changed file

bencodezen

pr closed time in a day

issue closedvuejs/docs-next

Provide / Inject: Use readonly

In https://v3.vuejs.org/guide/composition-api-provide-inject.html

This is the current example for allowing components in which the object is injected to change the object.

  const book = reactive({
    title: 'Vue 3 Guide',
    author: 'Vue Team'
  })

  function changeBookName() {
    book.title = 'Vue 3 Advanced Guide'
  }

  provide('book', book)
  provide('changeBookName', changeBookName)

I believe that best practice would be to mark the book as readonly and force the use of the setter that way:

  const book = reactive({
    title: 'Vue 3 Guide',
    author: 'Vue Team'
  })

  function changeBookName() {
    book.title = 'Vue 3 Advanced Guide'
  }

  // NEW
  // readonly prevents direct mutation of book  and forces the use of the changeBookName function.
  provide('book', readonly(book))
  provide('changeBookName', changeBookName)

(and btw, this warning should best be placed in the normal provide/inject guide)

closed time in a day

michaelzangl

pull request commentvuejs/docs-next

docs (#391): update provide inject in composition api with enhanced reactivity

Thanks for the review and feedback @phanan!

bencodezen

comment created time in a day

issue commentvuejs/docs-next

Improve clarity on using Symbol with provide / inject

Thanks for the feedback @vvanpo! I'm checking with the team to make sure we clarify how this is defined and will get back to you once I get an answer!

vvanpo

comment created time in a day

push eventcypress-io/cypress-documentation

Ben Hong

commit sha 9cf615ee16aab85c6f50c7dd8b79a44aaa24a4ee

docs: fix description

view details

Ben Hong

commit sha cbce5a4bed92a09041f455cfda225e4058ee3c70

docs: add views by documentation

view details

Ben Hong

commit sha 1ef5cdc5f5004d63da3ed410f57d471a1858d0f4

docs: bump heading hierarchy

view details

Ben Hong

commit sha 2c3d1e081d1318260d2492e6fd9fbb1b10a58c38

docs: update test case history screenshot

view details

Ben Hong

commit sha 8a8ec233c4dcc97a7075b3cea5c3aa9247385606

docs: update test case history description

view details

push time in a day

Pull request review commentcypress-io/cypress-documentation

docs/dashboard test history updates

 Unique tests and number of spec files are computed respective of the filters sel {% imgTag /img/dashboard/analytics/dashboard-analytics-test-suite-size-table.png "Dashboard Analytics Test Suite Size Table Screenshot" %}  A table of results grouped by date for the time range filter is displayed with unique tests and spec files.++## Top Failures++{% imgTag /img/dashboard/analytics/dashboard-analytics-top-failures.png "Dashboard Analytics Top Failures Screenshot" %}++This report shows the top failures in your test suite.++### Filters

Good catch. I'll update the rest of the docs

bencodezen

comment created time in a day

Pull request review commentcypress-io/cypress-documentation

docs/dashboard test history updates

 Runs that have been canceled or are in an errored state can be archived from the   `https://dashboard.cypress.io/projects/{project ID}/runs/{run number}` - Click **{% fa fa-history %} Restore from archive**   {% imgTag /img/dashboard/restore-from-archive.png "restore-from-archive" %}++## Test Case History

Good idea!

bencodezen

comment created time in a day

Pull request review commentcypress-io/cypress-documentation

docs/dashboard test history updates

 Unique tests and number of spec files are computed respective of the filters sel {% imgTag /img/dashboard/analytics/dashboard-analytics-test-suite-size-table.png "Dashboard Analytics Test Suite Size Table Screenshot" %}  A table of results grouped by date for the time range filter is displayed with unique tests and spec files.++## Top Failures++{% imgTag /img/dashboard/analytics/dashboard-analytics-top-failures.png "Dashboard Analytics Top Failures Screenshot" %}++This report shows the top failures in your test suite.++### Filters++{% imgTag /img/dashboard/analytics/dashboard-analytics-top-failures-filters.png "Dashboard Analytics Top Failures Filters Screenshot" %}++Results may be filtered by:++- Branch+- Tag+- Time Range+- Run Group+- Committer+- Spec File+- Browser+- Cypress Version+- Operating System++### Results++{% imgTag /img/dashboard/analytics/dashboard-analytics-top-failures-graph.png "Dashboard Analytics Top Failures Graph Screenshot" %}++The average test suite size over time is displayed respective of the filters selected.

Good catch. Thanks!

bencodezen

comment created time in a day

push eventvuejs/docs-next

Ben Hong

commit sha 5b4dd017a5fa46dd9aa67033ea58329e74f82cdf

docs: integrate tip into content

view details

push time in a day

Pull request review commentvuejs/docs-next

docs (#391): update provide inject in composition api with enhanced reactivity

 # Provide / Inject -> This guide assumes that you have already read the [Composition API Introduction](composition-api-introduction.html) and [Reactivity Fundamentals](reactivity-fundamentals.html). Read that first if you are new to Composition API.+> This guide assumes that you have already read [Provide / Inject](component-provide-inject.html), [Composition API Introduction](composition-api-introduction.html), and [Reactivity Fundamentals](reactivity-fundamentals.html).  We can use [provide / inject](component-provide-inject.html) with the Composition API as well. Both can only be called during [`setup()`](composition-api-setup.html) with a current active instance. -For example, if we want to provide a book name on the root component and inject it on the child component:+## Scenario Background -```js-import { provide, inject } from 'vue'+Let's assume that we want to rewrite the following code, which contains a `MyMap` component that provides a `MyMarker` component with the user's location, using the Composition API.++```vue+<!-- src/components/MyMap.vue -->+<template>+  <MyMarker />+</template>++<script>+import MyMarker from './MyMarker.vue'++export default {+  components: {+    MyMarker+  },+  provide: {+    location: 'North Pole',+    geolocation: {+      longitude: 90,+      latitude: 135+    }+  }+}+</script>+```++```vue+<!-- src/components/MyMarker.vue -->+<script>+export default {+  inject: ['location', 'longitude', 'latitude']+}+</script>+```++## Using Provide++When using `provide` in `setup()`, we start by explicitly importing the method from `vue`. This allows us to define each property with its own invocation of `provide`.++The `provide` function allows you to define the property through two parameters:++1. The property's name (`<String>` type)+2. The property's value -const RootComponent = {+Using our `MyMap` component, our provided values can be refactored as the following:++```vue{7,14-20}

I'm a little confused. Are you saying we shouldn't use line highlighting? Or are you recommending splitting it up into HTML and JS for easier maintenance?

bencodezen

comment created time in a day

Pull request review commentvuejs/docs-next

docs (#391): update provide inject in composition api with enhanced reactivity

 # Provide / Inject -> This guide assumes that you have already read the [Composition API Introduction](composition-api-introduction.html) and [Reactivity Fundamentals](reactivity-fundamentals.html). Read that first if you are new to Composition API.+> This guide assumes that you have already read [Provide / Inject](component-provide-inject.html), [Composition API Introduction](composition-api-introduction.html), and [Reactivity Fundamentals](reactivity-fundamentals.html).  We can use [provide / inject](component-provide-inject.html) with the Composition API as well. Both can only be called during [`setup()`](composition-api-setup.html) with a current active instance. -For example, if we want to provide a book name on the root component and inject it on the child component:+## Scenario Background -```js-import { provide, inject } from 'vue'+Let's assume that we want to rewrite the following code, which contains a `MyMap` component that provides a `MyMarker` component with the user's location, using the Composition API.++```vue+<!-- src/components/MyMap.vue -->+<template>+  <MyMarker />+</template>++<script>+import MyMarker from './MyMarker.vue'++export default {+  components: {+    MyMarker+  },+  provide: {+    location: 'North Pole',+    geolocation: {+      longitude: 90,+      latitude: 135+    }+  }+}+</script>+```++```vue+<!-- src/components/MyMarker.vue -->+<script>+export default {+  inject: ['location', 'longitude', 'latitude']+}+</script>+```++## Using Provide++When using `provide` in `setup()`, we start by explicitly importing the method from `vue`. This allows us to define each property with its own invocation of `provide`.++The `provide` function allows you to define the property through two parameters:++1. The property's name (`<String>` type)+2. The property's value -const RootComponent = {+Using our `MyMap` component, our provided values can be refactored as the following:++```vue{7,14-20}+<!-- src/components/MyMap.vue -->+<template>+  <MyMarker />+</template>++<script>+import { provide } from 'vue'+import MyMarker from './MyMarker.vue++export default {+  components: {+    MyMarker+  },   setup() {-    provide('book', 'Vue 3 guide')+    provide('location', 'North Pole')+    provide('geolocation', {+      longitude: 90,+      latitude: 135+    })   } }+</script>+```++## Using Inject++When using `inject` in `setup()`, we also need to explicitly import it from `vue`. Once we do so, this allows us to invoke it to define how we want to expose it to our component.++The `inject` function takes two parameters: -const MyBook = {+1. The name of the property to inject+2. A default value (**Optional**)++Using our `MyMarker` component, we can refactor it with the following code:++```vue{3,6-14}+<!-- src/components/MyMarker.vue -->+<script>+import { inject } from 'vue'++export default {   setup() {-    const book = inject(-      'book',-      'Eloquent Javascript' /* optional default value */-    )+    const userLocation = inject('location', 'The Universe')+    const userGeolocation = inject('geolocation')+     return {-      book+      userLocation,+      userGeolocation     }   } }+</script> ``` -`inject` accepts an optional default value as the 2nd argument. If a default value is not provided and the property is not found on the provide context, `inject` returns `undefined`.+## Reactivity++### Adding Reactivity++To add reactivity between provided and injected values, we can use a [ref](reactivity-fundamentals.html#creating-standalone-reactive-values-as-refs) or [reactive](reactivity-fundamentals.html#declaring-reactive-state) when providing a value.++Using our `MyMap` component, our code can be updated as follows: -If we need to provide or inject multiple values, we can do this with a subsequent call of `provide` or `inject` respectively:+```vue{7,15-22}+<!-- src/components/MyMap.vue -->+<template>+  <MyMarker />+</template> -```js{5-6,12-16}-import { provide, inject } from 'vue'+<script>+import { provide, reactive, ref } from 'vue'+import MyMarker from './MyMarker.vue -const RootComponent = {+export default {+  components: {+    MyMarker+  },   setup() {-    provide('book', 'Vue 3 guide')-    provide('year', '2020')+    const location = ref('North Pole')+    const geolocation = reactive({+      longitude: 90,+      latitude: 135+    })++    provide('location', location)+    provide('geolocation', geolocation)   } }+</script>+```++Now, if anything changes in either property, the `MyMarker` component will automatically be updated as well!++### Mutating Reactive Properties++When using reactive provide / inject values, **it is recommended to keep any mutations to reactive properties inside of the _provider_ whenever possible**.++For example, in the event we needed to change the user's location, we would ideally do this inside of our `MyMap` component.++```vue{28-32}+<!-- src/components/MyMap.vue -->+<template>+  <MyMarker />+</template>++<script>+import { provide, reactive, ref } from 'vue'+import MyMarker from './MyMarker.vue -const MyBook = {+export default {+  components: {+    MyMarker+  },   setup() {-    const book = inject(-      'book',-      'Eloquent Javascript' /* optional default value */-    )-    const year = inject('year')+    const location = ref('North Pole')+    const geolocation = reactive({+      longitude: 90,+      latitude: 135+    })++    provide('location', location)+    provide('geolocation', geolocation)      return {-      book,-      year+      location+    }+  },+  methods: {+    updateLocation() {+      this.location = 'South Pole'     }   } }+</script> ``` -## Injection Reactivity+However, there are times where we need to update the data inside of the component where the data is injected. In this scenario, we recommend providing a method that is responsible for mutating the reactive property. -To retain reactivity between provided and injected values, we can use a [ref](reactivity-fundamentals.html#creating-standalone-reactive-values-as-refs) or [reactive](reactivity-fundamentals.html#declaring-reactive-state) when providing a value:+```vue{21-23,27}+<!-- src/components/MyMap.vue -->+<template>+  <MyMarker />+</template> -```js-import { ref, reactive } from 'vue'--// in provider-setup() {-  const book = reactive({-    title: 'Vue 3 Guide',-    author: 'Vue Team'-  })-  const year = ref('2020')--  provide('book', book)-  provide('year', year)-}+<script>+import { provide, reactive, ref } from 'vue'+import MyMarker from './MyMarker.vue -// in consumer-setup() {-  const book = inject('book')-  const year = inject('year')+export default {+  components: {+    MyMarker+  },+  setup() {+    const location = ref('North Pole')+    const geolocation = reactive({+      longitude: 90,+      latitude: 135+    })++    const updateLocation = () => {+      location.value = 'South Pole'+    } -  return { book, year }+    provide('location', location)+    provide('geolocation', geolocation)+    provide('updateLocation', updateLocation)+  } }+</script> ``` -Now, when either `book` or `year` are changed on the _provider_ component, we can observe them changing on the component where they are injected.--::: warning-We don't recommend mutating a reactive property where it's injected as it's breaking Vue one-direction data flow. Instead, try to either mutate values where they are _provided_ or provide a method to mutate them--```js-import { ref, reactive } from 'vue'+```vue{9,14}+<!-- src/components/MyMarker.vue -->+<script>+import { inject } from 'vue' -// in provider-setup() {-  const book = reactive({-    title: 'Vue 3 Guide',-    author: 'Vue Team'-  })+export default {+  setup() {+    const userLocation = inject('location', 'The Universe')+    const userGeolocation = inject('geolocation')+    const updateUserLocation = inject('updateUserLocation') -  function changeBookName() {-    book.title = 'Vue 3 Advanced Guide'+    return {+      userLocation,+      userGeolocation,+      updateUserLocation+    }   }--  provide('book', book)-  provide('changeBookName', changeBookName) }+</script>+``` -// in consumer-setup() {-  const book = inject('book')-  const changeBookName = inject('changeBookName')+:::tip

I was debating this too. With your recommendation, let me blend it in better

bencodezen

comment created time in a day

push eventcypress-io/cypress-documentation

Ben Hong

commit sha 16b0dab3676ab350c35fe910339169dc5f92ddbd

style: remove random new line

view details

Ben Hong

commit sha e18388ae2824339569a1838ecccba1c9896377dd

docs: remove unnecessary h1s

view details

Ben Hong

commit sha 212df4fe4d09c6deff8d2f821ac3f5fc84077c89

docs: update images without beta tags

view details

Ben Hong

commit sha a33f8386cfb770d583dfd9e2257de8c42558212d

docs: remove references to beta for dashboard analytics

view details

Ben Hong

commit sha 6d57da84ed0d5f0686799f69db2c9f242dcd69db

content: update dashboard content

view details

push time in a day

issue closedvuejs/docs-next

v3.vuejs.org guide on Composition API Introduction has typo

Hi, I believe this has typo mistake, may I make PR to fix this? Thanks

`methods: {

getUserRepositories () {
  // using `this.user` to fetch user repositories
}, // 2

updateFilters () { ... }, // 3

},`

getUserRepositories should be responsibility no#1

closed time in a day

ferry77

push eventvuejs/docs-next

Ferry Haryadi

commit sha aaef662160d2f627061a35594fe568aa87b706fa

docs: correct example scenario comment in Composition API intro example (#395)

view details

push time in a day

PR merged vuejs/docs-next

Fixing typo in Composition API intro example

CC @bencodezen , Thanks

+1 -1

0 comment

1 changed file

ferry77

pr closed time in a day

PR closed vuejs/vuejs.org

Update mainpage

Please ignore this PR, or delete it.

+7096 -6476

0 comment

84 changed files

thefumigator

pr closed time in a day

issue commentvuejs/docs-next

UI bug with code preview

@theamanjs I just checked as well and agree with @marina-mosti's findings in being unable to reproduce the issue on Chrome, Firefox or Safari.

theamanjs

comment created time in a day

push eventvuejs/docs-next

Ben Hong

commit sha 38c72c441e52f632fee12f7e8d2caf873b584853

docs: fix grammar in disclaimer

view details

push time in a day

push eventvuejs/docs-next

Ben Hong

commit sha ce436444d1a4fe6c736d233d57372f292c774c65

docs: fix imports

view details

Ben Hong

commit sha 803ef6667ad2769ff03aeebb7a5d74a109c52db6

docs: remove unnecessary qualifier

view details

push time in a day

push eventvuejs/docs-next

Ben Hong

commit sha b9a819bbc53cae57ccada3277d186ddc4526ff26

docs: update disclaimer for provide inject composition api

view details

push time in 2 days

create barnchvuejs/docs-next

branch : docs/391-provide-inject-readonly

created branch time in 2 days

push eventbencodezen/vue-3-playground

Ben Hong

commit sha 378ac81f3a7d94f9f0585bdd3c3e61b1cca6bacf

feature: play around with provide inject

view details

push time in 2 days

create barnchbencodezen/vue-3-playground

branch : master

created branch time in 2 days

created repositorybencodezen/vue-3-playground

created time in 2 days

create barnchbencodezen/vue-3-playground

branch : master

created branch time in 2 days

created repositorybencodezen/vue-3-playground

created time in 2 days

issue commentvuejs/docs-next

v3.vuejs.org guide on Composition API Introduction has typo

@ferry77 Just reviewed this too. Feel free to issue a PR as well. Thanks again for asking!

ferry77

comment created time in 2 days

issue commentvuejs/docs-next

Add Mobile section to the docs

@mhartington Looks like a great start! Thanks for getting this to us 👍

bencodezen

comment created time in 2 days

issue closedvuejs/docs-next

v3.vuejs.org guide on destructuring slot has typo

Hi, I believe this has typo mistake, may I made a PR to fix? Thank you.

You can even define fallbacks, to be used in case a slot prop is undefined:

<todo-list v-slot="{ item = 'Placeholder' }">
  <i class="fas fa-check"></i>
  <span class="green">{{ todo }}<span>
</todo-list>

It should says {{ item }} instead of {{ todo }}

closed time in 2 days

ferry77

PR merged vuejs/docs-next

fixing typo in slot prop fallback

CC @bencodezen I am very happy can do tiny contribution here :) Please let me know things I can improve next time.

+1 -1

0 comment

1 changed file

ferry77

pr closed time in 2 days

push eventvuejs/docs-next

Ferry Haryadi

commit sha 93019818019575d5bfc65b5afd9408a28feebb45

docs: fixing typo in slot prop fallback (#394)

view details

push time in 2 days

issue commentvuejs/docs-next

v3.vuejs.org guide on destructuring slot has typo

@ferry77 Thanks you for asking. Please feel free to issue a PR for this!

ferry77

comment created time in 2 days

push eventbencodezen/rust-playground

Ben Hong

commit sha 7e42f9042dd962bfaff8b379cd6260c86157f426

feature: add hello world script

view details

Ben Hong

commit sha 63e80a97f54ae7c39d16b6ed2fe16ca12aaa7a9d

chore: rename file

view details

Ben Hong

commit sha 809002906731d13bd2f2a504a965b5ee15c18521

feature: add hello_cargo project

view details

Ben Hong

commit sha bbb46be9a4a0d3c8aefdfadb2ae01bb79066ea5e

config: ignore all build files

view details

Ben Hong

commit sha 495dfb4b9c3e325a31065aa30787c9cdae80e258

feature: add guessing feature

view details

push time in 3 days

create barnchbencodezen/rust-playground

branch : master

created branch time in 3 days

created repositorybencodezen/rust-playground

created time in 3 days

Pull request review commentcypress-io/cypress-documentation

docs: 5.0.0 release docs test retries

 title: Retry-ability {% note info %} # {% fa fa-graduation-cap %} What you'll learn +- How Cypress retries tests - How Cypress retries commands and assertions - When commands are retried and when they are not - How to address some situations of flaky tests {% endnote %}  A core feature of Cypress that assists with testing dynamic web applications is retry-ability. Like a good transmission in a car, it usually works without you noticing it. But understanding how it works will help you write faster tests with fewer run-time surprises. +# Test retries++Tests retry by default during `cypress run` if they fail. Additionally, the number of retries can be configured. Read {% url "Test Retries" test-retries %} for more information.+

New changes made!

bencodezen

comment created time in 4 days

push eventcypress-io/cypress-documentation

Ben Hong

commit sha e0dc36ec7b219c04846f1eef27817f031aef9e23

docs: improve diction clarity Co-authored-by: Jessica Sachs <jess@jessicasachs.io>

view details

push time in 4 days

push eventcypress-io/cypress-documentation

Ben Hong

commit sha f772128e0d2b0b3c2bb726d1821be3784594dee0

docs: add call to action for test retries at the bottom

view details

push time in 4 days

Pull request review commentcypress-io/cypress-documentation

docs: 5.0.0 release docs test retries

 With the new test retries feature, Cypress will be able to retry failed tests to  ## How It Works -As of Cypress, test retries are on by default in `cypress run` mode. This means that tests will automatically be re-run up to two additional times (for a total of three attempts) before being marked as a failed test. When each test is run again, the following lifecycle hooks will be re-run on each attempt:+By default, tests being run in {% url "`cypress run`" command-line#cypress-run %} mode will automatically be retried up to 2 additional times (for a total of 3 attempts) before being marked as a failed test. When each test is run again, the following {% url "hooks" writing-and-organizing-tests#Hooks %} will be re-run on each attempt:

No longer relevant due to disabled default

bencodezen

comment created time in 4 days

push eventenjoythevue/website

Ben Hong

commit sha 6f5260bc7e3a67cfe8fe75870c40bb84b1b1cf52

content: update episode title

view details

push time in 5 days

issue commentvuejs/docs-next

Add to V2 migration docs about change in transition class names

@BenRutlandWeb Totally understandable. We hope to have an official section in the Migration Guide on transitions soon!

BenRutlandWeb

comment created time in 5 days

issue closedvuejs/vuepress

How to implement update tips

<!-- Please don't delete this template or we'll close your issue --> <!-- Before creating an issue please make sure you are using the latest version of VuePress. -->

Feature request

image

I've noticed that the vuepress website has a prompt when content is updated, and I'd like to know how to turn it on. <!-- Please ask questions on StackOverflow. --> <!-- https://stackoverflow.com/questions/ask?tags=vuepress --> <!-- Issues which contain questions or support requests will be closed. -->

closed time in 5 days

juzi214032

issue commentvuejs/vuepress

How to implement update tips

Hi @juzi214032! You can learn more about it here: https://vuepress.vuejs.org/plugin/official/plugin-pwa.html#options

Hope this helps!

juzi214032

comment created time in 5 days

issue commentvuejs/vuepress

Vue 3 support

@vvanpo As of right now, we are currently seeing how the status of VitePress goes for Vue 3 support. Once that is more stable, we'll have more official announcements regarding Vue 3 support for VuePress. Hope this helps!

vvanpo

comment created time in 5 days

push eventvuejs/vuejs.org

Ben Hong

commit sha cb67ece95c8ced81569347609549a0afd8592467

docs: update testing section with more comprehensive guidance (#2654)

view details

push time in 6 days

delete branch vuejs/vuejs.org

delete branch : docs/update-testing-section

delete time in 6 days

PR merged vuejs/vuejs.org

Reviewers
docs: update testing section with more comprehensive guidance

This is a direct copy and paste from the v3 docs to provide more comprehensive guidance around testing in the Vue.js ecosystem with one addition of the existing cookbook resource.

+172 -132

0 comment

2 changed files

bencodezen

pr closed time in 6 days

issue openedvuejs/docs-next

Add Mobile section to the docs

Given that mobile solutions are a popular request, it would be good to provide some guidance in this regard.

Things that come to mind include:

  • NativeScript
  • Capacitor

created time in 6 days

push eventOpenClassrooms-Student-Center/Project-10-Bank-API

Ben Hong

commit sha 50bdfb882747640cb7bb1afe9fcd9814083ba52f

docs: add design asset reference in GitHub issues

view details

push time in 6 days

push eventOpenClassrooms-Student-Center/Project-10-Bank-API

Ben Hong

commit sha b18bd6bc37a536a210bdf0e177a64566aebeb61b

docs: add design assets section to README

view details

push time in 6 days

push eventOpenClassrooms-Student-Center/Project-10-Bank-API

Ben Hong

commit sha 72ee750548aa2561c6ab8552768b735caead0f27

docs: add static design mockups and assets

view details

push time in 6 days

push eventvuejs/vuepress

Ben Hong

commit sha f04d14d9debd3735f341ad49ce4afb2b1dd6ea65

docs: remove deps updates

view details

Ben Hong

commit sha c7ba6162045bc88bb0aed09cb24257aad5b655dd

docs: remove workflow update

view details

push time in 6 days

release vuejs/vuepress

v1.5.3

released time in 6 days

release vuejs/vuepress

v1.5.2

released time in 6 days

release vuejs/vuepress

v1.5.1

released time in 6 days

push eventvuejs/vuepress

Ben Hong

commit sha 5706fb0eb792d85d31691ad7d3b048b1ea9b09de

chore: version 1.5.3 changelog

view details

push time in 6 days

created tagvuejs/vuepress

tagv1.5.3

📝 Minimalistic Vue-powered static site generator

created time in 6 days

push eventvuejs/vuepress

Ben Hong

commit sha 94dfb757224173c2a2bfdeece6ca690e85036757

build: release version 1.5.3

view details

push time in 6 days

PR closed vuejs/vuepress

fix($theme-vue): carbon ads loading issue

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

Summary

What kind of change does this PR introduce? (check at least one)

  • [x] Bugfix
  • [ ] Feature
  • [ ] Code style update
  • [ ] Refactor
  • [ ] Docs
  • [ ] Build-related changes
  • [ ] Other, please describe:

If changing the UI of default theme, please provide the before/after screenshot:

Does this PR introduce a breaking change? (check one)

  • [ ] Yes
  • [ ] No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

  • [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

You have tested in the following browsers: (Providing a detailed version will be better.)

  • [ ] Chrome
  • [ ] Firefox
  • [ ] Safari
  • [ ] Edge
  • [ ] IE

If adding a new feature, the PR's description includes:

  • [ ] A convincing reason for adding this feature
  • [ ] Related documents have been updated
  • [ ] Related tests have been updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.

Other information:

+5 -2

1 comment

1 changed file

bencodezen

pr closed time in 6 days

pull request commentvuejs/vuepress

fix($theme-vue): carbon ads loading issue

Disregard. Mis-diagnosis of issue

bencodezen

comment created time in 6 days

PR opened vuejs/vuepress

fix($theme-vue): carbon ads loading issue

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

Summary

What kind of change does this PR introduce? (check at least one)

  • [x] Bugfix
  • [ ] Feature
  • [ ] Code style update
  • [ ] Refactor
  • [ ] Docs
  • [ ] Build-related changes
  • [ ] Other, please describe:

If changing the UI of default theme, please provide the before/after screenshot:

Does this PR introduce a breaking change? (check one)

  • [ ] Yes
  • [ ] No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

  • [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

You have tested in the following browsers: (Providing a detailed version will be better.)

  • [ ] Chrome
  • [ ] Firefox
  • [ ] Safari
  • [ ] Edge
  • [ ] IE

If adding a new feature, the PR's description includes:

  • [ ] A convincing reason for adding this feature
  • [ ] Related documents have been updated
  • [ ] Related tests have been updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.

Other information:

+5 -2

0 comment

1 changed file

pr created time in 6 days

push eventvuejs/vuepress

Ben Hong

commit sha 0e6242bfc4d7587771babbeb88fbe4445390f0fc

fix($theme-vue): carbon ads loading issue

view details

push time in 6 days

create barnchvuejs/vuepress

branch : fix/carbon-ad-loading-issue

created branch time in 6 days

push eventvuejs/docs-next

Ben Hong

commit sha 101d5573ef0fe69cfcc3d8cd08706670c1d0e202

docs: clarify example and match computed definition to function (#376) * docs: clarify example and match computed definition to function * fix: update variable name

view details

push time in 7 days

push eventvuejs/docs-next

GeorgeZou

commit sha 1d9fa0ca3deb31d7be760477dfef28c6e7f547df

docs: updated version (#380)

view details

push time in 7 days

PR merged vuejs/docs-next

fix: updated version

fix: updated version

+1 -1

0 comment

1 changed file

georgezouq

pr closed time in 7 days

push eventcypress-io/cypress-documentation

Ben Hong

commit sha da403661f945803cd419339336df174ffb9f76c3

docs: update with new default of 0

view details

push time in 8 days

push eventOpenClassrooms-Student-Center/Project-10-Bank-API

Ben Hong

commit sha 4314f9cf1919c8c7dff68536efd9c3bc849d46d3

feature: add styles for hero and navigation

view details

Ben Hong

commit sha 5afb526c377edf7251dffed0bd3c2c7ced781e27

feature: finish home page desktop layout

view details

Ben Hong

commit sha 77bc21b880c1503db9c5a222b63c7acc78c01bbd

feature: add responsive design for home page

view details

Ben Hong

commit sha d1a0086063e528a27bb2864467e51ad96abf4cf6

fix: footer position bottom

view details

Ben Hong

commit sha f8deb2e3f71e5b54a28407159bbbef039487f906

feature: add styles for sign in page

view details

Ben Hong

commit sha ded03cf73277392114cbbdbf5d634738a0f1f0a0

feature: add designs for user page

view details

Ben Hong

commit sha 9fbfa2a67ad42feaa279912f42116f19f1c15f00

feature: update nav item on log-in

view details

push time in 8 days

more