Git Product home page Git Product logo

testing-library-docs's Introduction

@testing-library/angular

Octopus with the Angular logo

Simple and complete Angular testing utilities that encourage good testing practices.


Read The Docs | Edit the docs



Build Status version downloads MIT License

All Contributors PRs Welcome Code of Conduct Discord

Watch on GitHub Star on GitHub Tweet

Open in GitHub Codespaces

Table of Contents

The problem

You want to write maintainable tests for your Angular components. As a part of this goal, you want your tests to avoid including implementation details of your components and rather focus on making your tests give you the confidence for which they are intended. As part of this, you want your testbase to be maintainable in the long run so refactors of your components (changes to implementation but not functionality) don't break your tests and slow you and your team down.

This solution

The @testing-library/angular is a very lightweight solution for testing Angular components. It provides light utility functions on top of Angular and @testing-library/dom, in a way that encourages better testing practices. Its primary guiding principle is:

The more your tests resemble the way your software is used, the more confidence they can give you.

Example

counter.component.ts

@Component({
  selector: 'app-counter',
  template: `
    <button (click)="decrement()">-</button>
    <span>Current Count: {{ counter }}</span>
    <button (click)="increment()">+</button>
  `,
})
export class CounterComponent {
  @Input() counter = 0;

  increment() {
    this.counter += 1;
  }

  decrement() {
    this.counter -= 1;
  }
}

counter.component.spec.ts

import { render, screen, fireEvent } from '@testing-library/angular';
import { CounterComponent } from './counter.component';

describe('Counter', () => {
  test('should render counter', async () => {
    await render(CounterComponent, { componentProperties: { counter: 5 } });

    expect(screen.getByText('Current Count: 5'));
  });

  test('should increment the counter on click', async () => {
    await render(CounterComponent, { componentProperties: { counter: 5 } });

    const incrementButton = screen.getByRole('button', { name: '+' });
    fireEvent.click(incrementButton);

    expect(screen.getByText('Current Count: 6'));
  });
});

See more examples

Installation

This module is distributed via npm which is bundled with node and should be installed as one of your project's devDependencies:

npm install @testing-library/angular --save-dev

You may also be interested in installing jest-dom so you can use the custom jest matchers.

Docs

Version compatibility

Angular Angular Testing Library
18.x 16.x, 15.x, 14.x, 13.x
17.x 16.x, 15.x, 14.x, 13.x
16.x 14.x, 13.x
>= 15.1 14.x, 13.x
< 15.1 12.x, 11.x
14.x 12.x, 11.x

Guiding Principles

The more your tests resemble the way your software is used, the more confidence they can give you.

We try to only expose methods and utilities that encourage you to write tests that closely resemble how your Angular components are used.

Utilities are included in this project based on the following guiding principles:

  1. If it relates to rendering components, it deals with DOM nodes rather than component instances, nor should it encourage dealing with component instances.
  2. It should be generally useful for testing individual Angular components or full Angular applications.
  3. Utility implementations and APIs should be simple and flexible.

At the end of the day, what we want is for this library to be pretty light-weight, simple, and understandable.

Contributors

Thanks goes to these people (emoji key):

Tim Deschryver
Tim Deschryver

๐Ÿ’ป ๐Ÿ“– ๐Ÿš‡ โš ๏ธ
Michaรซl De Boey
Michaรซl De Boey

๐Ÿ“–
Ignacio Le Fluk
Ignacio Le Fluk

๐Ÿ’ป โš ๏ธ
Tamรกs Szabรณ
Tamรกs Szabรณ

๐Ÿ’ป
Gregor Woiwode
Gregor Woiwode

๐Ÿ’ป
Toni Villena
Toni Villena

๐Ÿ› ๐Ÿ’ป ๐Ÿ“– โš ๏ธ
ShPelles
ShPelles

๐Ÿ“–
Miluoshi
Miluoshi

๐Ÿ’ป โš ๏ธ
Nick McCurdy
Nick McCurdy

๐Ÿ“–
Srinivasan Sekar
Srinivasan Sekar

๐Ÿ“–
Bitcollage
Bitcollage

๐Ÿ“–
Emil Sundin
Emil Sundin

๐Ÿ’ป
Ombrax
Ombrax

๐Ÿ’ป
Rafael Santana
Rafael Santana

๐Ÿ’ป โš ๏ธ ๐Ÿ›
Benjamin Blackwood
Benjamin Blackwood

๐Ÿ“– โš ๏ธ
Gustavo Porto
Gustavo Porto

๐Ÿ“–
Bo Vandersteene
Bo Vandersteene

๐Ÿ’ป
Janek
Janek

๐Ÿ’ป โš ๏ธ
Gleb Irovich
Gleb Irovich

๐Ÿ’ป โš ๏ธ
Arjen
Arjen

๐Ÿ’ป ๐Ÿšง
Suguru Inatomi
Suguru Inatomi

๐Ÿ’ป ๐Ÿค”
Amit Miran
Amit Miran

๐Ÿš‡
Jan-Willem Willebrands
Jan-Willem Willebrands

๐Ÿ’ป
Sandro
Sandro

๐Ÿ’ป ๐Ÿ›
Michael Westphal
Michael Westphal

๐Ÿ’ป โš ๏ธ
Lukas
Lukas

๐Ÿ’ป
Matan Borenkraout
Matan Borenkraout

๐Ÿšง
mleimer
mleimer

๐Ÿ“– โš ๏ธ
MeIr
MeIr

๐Ÿ› โš ๏ธ
John Dengis
John Dengis

๐Ÿ’ป โš ๏ธ
Rokas Brazdลพionis
Rokas Brazdลพionis

๐Ÿ’ป
Mateus Duraes
Mateus Duraes

๐Ÿ’ป
Josh Joseph
Josh Joseph

๐Ÿ’ป โš ๏ธ
Torsten Knauf
Torsten Knauf

๐Ÿšง
antischematic
antischematic

๐Ÿ› ๐Ÿค”
Florian Pabst
Florian Pabst

๐Ÿ’ป
Mark Goho
Mark Goho

๐Ÿšง ๐Ÿ“–
Jan-Willem Baart
Jan-Willem Baart

๐Ÿ’ป โš ๏ธ

This project follows the all-contributors specification. Contributions of any kind welcome!

Docs

Read The Docs | Edit the docs

FAQ

I am using Reactive Forms and the jest-dom matcher toHaveFormValues always returns an empty object or there are missing fields. Why?

Only form elements with a name attribute will have their values passed to toHaveFormsValues.

Issues

Looking to contribute? Look for the Good First Issue label.

๐Ÿ› Bugs

Please file an issue for bugs, missing documentation, or unexpected behavior.

See Bugs

๐Ÿ’ก Feature Requests

Please file an issue to suggest new features. Vote on feature requests by adding a ๐Ÿ‘. This helps maintainers prioritize what to work on.

See Feature Requests

โ“ Questions

For questions related to using the library, please visit a support community instead of filing an issue on GitHub.

Getting started with GitHub Codespaces

To get started, create a codespace for this repository by clicking this ๐Ÿ‘‡

Open in GitHub Codespaces

A codespace will open in a web-based version of Visual Studio Code. The dev container is fully configured with software needed for this project.

Note: Dev containers is an open spec which is supported by GitHub Codespaces and other tools.

LICENSE

MIT

testing-library-docs's People

Contributors

afontcu avatar agentkma avatar alexkrolick avatar allcontributors[bot] avatar aryzing avatar bcarroll22 avatar benmonro avatar danieljcafonso avatar dependabot[bot] avatar eps1lon avatar erfanmirzapour avatar gpx avatar huyenltnguyen avatar kentcdodds avatar kierenhughes avatar m98 avatar matanbobi avatar mcous avatar meatnordrink avatar michaeldeboey avatar mihar-22 avatar nickmccurdy avatar olivierwilkinson avatar pablodinella avatar pedroapfilho avatar ph-fritsche avatar shemexelate avatar ssi02014 avatar timdeschryver avatar viniciusavieira avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

testing-library-docs's Issues

Alternate organization ideas

What are some ways that the current doc organization could be improved?

The shortcomings I see right now are:

  • Long nav list (could also be good, it's all on one page at least)
  • dom-testing-library setup and API is the main focus and dominates the nav structure; other wrappers refer to it. Implementations that don't rely on or have significant wrapping of the core library need additional treatment (e.g. ReasonReact and React Native).

Current Organization

TOP LEVEL: Docs, Help, Blog

Docs:

  • Getting Started
    • Introduction
    • Install
    • Example
    • Setup
    • Guiding Principles
  • Examples
    • Codesandbox Examples
    • Input Event
    • Update Props
    • React Context
    • React Intl
    • React Redux
    • React Router
    • Reach Router
    • React Transition Group
    • External Examples
  • API
    • Queries
    • Firing Events
    • Async Utilities
    • Helpers
  • Guides
    • Which query should I use?
    • Appearance and Disappearance
  • Frameworks
    • React Testing Library
      • Introduction
      • Example
      • Setup
      • API
      • FAQ
    • Cypress Testing Library
    • Vue Testing Library
    • Angular Testing Library
    • (Puppeteer Testing Library - missing)
    • (Preact Testing Library - missing)
    • ReasonReact Testing Library
      • Introduction
      • Examples
  • Ecosystem
    • user-event
    • jest-dom
    • bs-jest-dom
    • native-testing-library
  • Help
    • FAQ
    • Learning Material

Alt 1: Extract Examples and Guides

TOP LEVEL: Docs, Recipes, Help, Blog

  • Recipes
    • Examples
    • Guides
  • Docs
    • Move setup, API, and under a new DOM Testing Library section of Frameworks
    • RTL and other wrappers can still reference DTL content, but the docs would treat them as equal top-level entry points
    • Native Testing Library and ReasonReact Testing Library have more equal footing
  • Help
    • Move FAQ content here and give the pages a sidebar

@bcarroll22 @kentcdodds what do you think?

Broken link in Cypress examples

Describe the bug
The cypress-testing-library docs show some examples and link to a spec file in the repo, but the link is broken.

To Reproduce
Steps to reproduce the behavior:

  1. Go to https://testing-library.com/docs/cypress-testing-library/intro#examples
  2. Click on the link in the first paragraph under the "Examples" header
  3. See error:
    Screenshot 2019-03-15 13 48 08

Expected behavior
Link should take user to https://github.com/kentcdodds/cypress-testing-library/blob/master/cypress/integration/commands.spec.js

Main Issue for logging contributors on readme

Hey Everyone, this issue will be now used to log in any contributors who contribute to the testing-library docs.

๐ŸŽ‰ ๐ŸŽ‰ ๐ŸŽ‰

We have now configured the all-contributors bot for the same, and you can find all the documentation on how to use the bot to add contributors can be found here

a sample method on how to add contributors can be seen here
a sample PR created by the bot can be found here

the mods are requested to add any previous contributors and also to maybe edit this issue so that maybe you can pin this in the issues column.

/cc: @alexkrolick

Consider listing getAll queries explicitly in the API documentation

(re-filed from testing-library/dom-testing-library#200)

Problem description:

As a user, I would like quick access to the API documentation.

Sidebar at: https://testing-library.com/docs/api-queries
image

The sidebar lists all of the queries that are available, and is an easy reference when I'm deep in the middle of writing tests. However, the getAll functions are not explicitly listed. Since I'm writing tests, I'm looking to quickly get the information I need to accomplish my task, and missed the notices and sub-paragraphs about the getAll functions.

As a new user, I wrote the following in a test, since I didn't realize that these convenience functions existed.

verticalIndicators.querySelectorAll('[data-testid="vertical-indicator-line"]')

Suggested solution:

List all available API methods in the sidebar.

Broken links for vue-testing-library examples

Describe the bug
There are 4 broken links in /docs/vue-testing-library/examples#more-examples

To Reproduce
Steps to reproduce the behavior:

  1. Go to vue-testing-library -> examples -> more examples
  2. Click on one of the links of the section
  3. They redirect to a github 404

Expected behavior
Go to the expected file in the repository

ByAltText examples seem incorrect

Describe the bug
The example for ByAltText uses the following example markup:

<img alt="Incredibles 2 Poster" src="/incredibles-2.png" />

The examples pass /incredibles.*png$/i to getByAltText, which seems incorrect. If we're trying to find the element by the value of the alt attribute, why would we include png$ in the regular expression, since that's part of the src attribute and not the alt attribute?

To Reproduce
Steps to reproduce the behavior:

  1. Go to https://testing-library.com/docs/dom-testing-library/api-queries#byalttext
  2. Scroll down to the ByAltText example, if it isn't already visible
  3. Look at the example code

Expected behavior
I would expect the example to use "Incredibles 2 Poster", /incredibles/i, or something without the "png" as the argument to getByAltText.

If /incredibles.*png$/i is somehow correct, then perhaps a note explaining why that works would be helpful.

Screenshots
image

Desktop (please complete the following information):
N/A

Smartphone (please complete the following information):
N/A

Additional context
I haven't used this library yet, so maybe /incredibles.*png$/i is perfectly valid here. If it is, it is confusing, though.

Broken documentation links for render and fireEvent

Describe the bug
The links to render and fireEvent under Wrappers > React Testing Library > Example are broken.

To Reproduce
Steps to reproduce the behavior:

  1. Go to here
  2. Click on the link render and/or fireEvent
  3. See error

Expected behavior
I think render and fireEvent should lead to somewhere? These links just seem to be broken.

Screenshots
screen shot 2019-02-26 at 6 46 29 pm
screen shot 2019-02-26 at 6 46 52 pm

Desktop (please complete the following information):

  • OS: macOS High Sierra
  • Browser: Safari
  • Version 12.0.3

RFC: Native docs merge

Is your feature request related to a problem? Please describe.
Nope, promised I'd be back to talk about this with a plan though ๐Ÿ˜‰

Describe the solution you'd like
I'd like to merge the docs sites. Seems very doable now.

Describe alternatives you've considered
Not merging the docs sites ๐Ÿคทโ€โ™‚๏ธ

Additional context
Alright here we go. Here's the content hierarchy I'm proposing:

Topnav

  • DOM
  • Native
  • Ecosystem
  • Help
  • Blog

Sidebars

  • DOM
    • Getting started
    • Main API
    • Wrapper APIs
    • Examples
  • Native
    • Getting started
    • API
    • Examples
  • Ecosystem
    • user-event
    • jest-dom
    • bs-jest-dom
    • jest-native
  • Help
    • Guides
      • Which query:
        • Make it more generic so that it applies to DOM and Native
      • Appearance and disappearance
        • Make it more generic so that it applies to DOM and Native
    • Learning material
    • Contributing

I know it's quite a bit different than current state, but the content of most things doesn't need to change. It's mostly re-organizing the making some references more generic (which I mostly addressed in my latest PR.

I took a couple screenshots of how the topnav would look with these items at different sizes:

Screen Shot 2019-04-28 at 10 33 47 PM

Screen Shot 2019-04-28 at 10 34 51 PM

So I think it looks really nice! And this would allow us both to have the amount of docs we'd need for users to have the same great experience.

This is intended to be a first draft, let me know what you guys think. I think in this model I could pretty much just copy the native docs over without many changes.

React Testing Library - Full Example shows deprecated version of jest-dom/extend-expect

React Testing Library Example Code Snippet shows deprecated version of jest-dom/extend expect import

The current Full Example code snippet shows:
import 'jest-dom/extend-expect'

BUT

that is the deprecated version of jest-dom/extend-expect AND should show

import { expect } from '@testing-library/jest-dom'
To Reproduce
Steps to reproduce the behavior:

  1. Go to 'https://testing-library.com/docs/react-testing-library/example-intro'
  2. Scroll down to 'React Testing Library Example sections.'
  3. See error

Expected behavior
show current version of jest-dom with expect destructured from import

Screenshots
If applicable, add screenshots to help explain your problem.

Screen Shot 2019-07-17 at 9 34 38 PM

Additional context
Add any other context about the problem here.

SyntaxError: Unexpected identifier

I'm have one problem with typescript:

`Test suite failed to run

F:\hugo\snack\node_modules\react-swipe-component\lib\index.js:14
import React from 'react';
       ^^^^^

SyntaxError: Unexpected identifier

   7 | import Form from './components/Form';
   8 | import List from './components/List';
>  9 | import { Swipe } from "react-swipe-component"
     | ^
  10 | import { connect } from 'react-redux';
  11 |
  12 | interface Props {

  at ScriptTransformer._transformAndBuildScript (node_modules/@jest/transform/build/ScriptTransformer.js:471:17)
  at ScriptTransformer.transform (node_modules/@jest/transform/build/ScriptTransformer.js:513:25)
  at Object.<anonymous> (src/components/Client/index.tsx:9:1)`

Someone help-me

Set scroll position after navigation

More of a docusaurus issue, but it would be nice if the left navigation bar would either restore its position after navigation, or scroll to the selected navigation item. The second option is probably better so that external links would focus the current page in the nav tree.

Updates for the new scoped packages

I believe most official packages are being migrated over to the scoped version and we need to update the docs to reflect this change.

Also, when talking about dom-testing-library, react-testing-library, and cypress-testing-library. I'm now referring to it as DOM Testing Library, React Testing Library, and Cypress Testing Library. The only time it should appear as @testing-library/dom is when we're talking about the module.

We'll need to update code samples as well as prose text throughout the docs.

I don't think we have to do it all at once, but if people could go around and update things a page/file at a time, that would be helpful!

update internal links

Got most of the content from the README organized and split up into files, but the internal links that used to point to README headers need to be updated

Implement textlint

I suggest adding textlint to the docs. It is a natural text linting tool that would help us (1) provide a consistent style across docs (2) help keep new additions on track.

You can see a PR implementing textlint here.

What do you think about it? I could open up a draft PR so we'd be able to discuss rules and nuances.

Unclear example for `ByLabelText`

Describe the bug
The example provided in the ByLabelText section does not seem to match the surrounding description

To Reproduce
If you go to the link above, the surrounding description states that

The example below will find the input node for the following DOM structures

yet there is no input node in the following part of the code snippet in the example

// The aria-labelledby attribute with non-form elements
<section aria-labelledby="section-one-header">
  <h3 id="section-one-header">Section One</h3>
  <p>some content</p>
</section>

Expected behavior
Unsure, although was expecting to see some kind of input element in the snippet above.

Add a page of resources for migrating from Enzyme to RTL

I think it'd be worth adding a page of links for people trying to migrate their tests from Enzyme.

I'd like to create this page, but I'm not sure where to put it, so I'll put the content here for now.

Case Studies / Tutorials

Videos

Reference implementations

Make the current page more obvious

Right now it's a little hard to tell which page I'm currently on.

image

Do you think we could make the current page red (maybe the same color as the octopus?)

image

Though that's probably not very accessible, so maybe underlined as well?

image

But that may not be enough either... What about an arrow indicator?

image

Or... maybe... even better...

image

๐Ÿ˜‚

(docs) Remove vue setup document global config section

Describe the bug
With the deprecation of the cleanup-after-each.js the documentation should be updated to remove the section referring to it.

To Reproduce
See https://github.com/testing-library/testing-library-docs/blob/master/docs/vue-testing-library/setup.md

Expected behavior
Delete the entire Global Config section

Screenshots

Desktop (please complete the following information):
N/A

Smartphone (please complete the following information):
N/A

Additional context

firstResultOrNull is not a function

Describe the bug
In the docs, https://testing-library.com/docs/dom-testing-library/api-helpers, it lists

const domTestingLib = require('@testing-library/dom')
const { queryHelpers } = domTestingLib

...

export function getByTestId(...args) {
  return queryHelpers.firstResultOrNull(getAllByTestId, ...args)
}

In updating from 'react-testing-library' v6 to '@testing-library/react' v8 and '@testing-library/dom' v5, this complains the function does not exist. I was able to get it working by looking at the original method in an older version and replicating it with:

function getByMyMethod(...args) {
    const result = getAllByMyMethod(...args);
    if (result.length === 0) {
        return null;
    }
    return result[0];
}

But the docs on the above link should be updated to exclude the function that is no longer supported.

Reorganize docs?

I know that we use Docusaurus, but as the list of different documentations grows, it's hard to keep adding new items here, and separate the documentation as it has to be.

I thought about we create a Gatsby Theme for it, one with all the correct parts for each different library, more focused on the lib itself, and not in a general way (as a React developer, I don't need to see the Vue testing-library, and vice-versa).

I would be happy to create the first POC.

Add native to the docs

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
First off, I love the new structure!

Here are my biggest questions with regards to getting native in the site:

  1. Queries aren't the same between native and dom. Should we make those more of a generic priority list and explain the reasoning? Maybe something like "Things a user can see", "Things that denote hierarchy", "Things hidden from users"
  2. Native doesn't have a DOM to observe, so on native all of the wait utils are the same. In fact, they don't even all exist. I only ported wait and waitForElement (for convenience). How should we handle that guide?
  3. The examples are roughly equivalent with the exception of routing and transition group. Should example titles be more generic? "Firing Events", "Updating Props", "Navigating" "Managing State" so that we can use code tabs to split native and dom?
  4. From the guiding principles: "If it relates to rendering components, it deals with DOM nodes" but native doesn't have DOM nodes. The big overarching question here is, would basically all pages need to be revised to take into account that testing-library is no longer about "DOM" or "documents" but about user experiences? Who should be the one to do those edits if yes?
  5. Once I got all of native's sections ported over (think basically every section under DOM Testing Library right now) the sidebar would actually be pretty long. It was nice to have everything easily accessible at first, but this may get really long. Do you think that would be overbearing? Maybe we'd want to just get it in and iterate?
  6. The ecosystems are platform specific, right? I don't want to mislead people into thinking user-event would work with native and cause lots of issues and requests for the maintainers of ecosystem components.

Overall though, huge update with lots of good work!

Describe alternatives you've considered
N/A

Additional context
Would the navbar title need to change to "Testing Library" from "DOM Testing Library"?

Framework specific docs

Describe the feature you'd like:
I introduced this at work a few months back and overall everyone loves it. The main complaint that I get from co-workers is that the docs make it hard to find answers when they don't know how to do something. I think the reason most are getting confused is because most of the docs are for dom-testing-library and it is not always clear how those methods map over to react-testing-library. It would be nice to have a docs site specifically for react-testing-library complete with examples of how to use each method specifically with React components.

Suggested implementation:
Write a site that using git book or some other technology that makes it easy to navigate all the queries and functions available.

Funding

Hey folks ๐Ÿ‘‹

I've been thinking about this a lot and I'd like to hear what people think about adding CodeFund to the site.

I think it's tricky to deal with money when there are various contributors to a project and it's not my intention for any of us to receive the money ourselves. Instead, I see this as an easy (and ethical) way to generate money which we could use to donate to good causes, another collective on Open Collective, and/or create stickers/merch we can hand out to people at conferences etc...

What do you all think?

More documentation for react-testing-library

Currently it seems like the best way to figure out what keys are available is to scrape through the code in the examples provided with the react-testing-library documentation or scrape through the internet. It would be nice to have ALL the keys available from react-testing library, render, container, etc. broken out kind of like how react props are explained in many react component libraries. For instance,

react-testing-libarary

  • render: renders the component
  • wait: waits for stuff (here it would be really good to explain why you would use wait. Not even sure how to properly use it )
  • fireEvent: click, change, etc and how to use each of them. There's really nothing out there except for what we found in an issue on how to use fireEvent.change. This makes unit testing really hard when you have to search the internet for these sorts of things. Also a good explanation of what to do after the fireEvent happens. It seems like sometimes the DOM changes in container and sometimes it doesn't and you have to use wait or waitForElement.
  • ...

render

  • container: dom stuff from the render
  • getByText: gets element by the text content of that element
  • ...

Safari: Website Fails to load code-block-buttons.css

Describe the bug

This occurs in safari, not able to replicate this for Firefox.

the css file code-block-buttons.css seems to be present and well inside the repository folder
here

But on loading the website, the console gives a 404 error on the file.
Screenshot 2019-04-29 at 11 18 45 AM

perplexed as to why the website is giving this error as the resource is present.
Would love to work on this as well ๐Ÿฅ‡

To Reproduce
Steps to reproduce the behavior:

  1. Load the website, and open up console.
  2. Open above provided link for the css file in the repo

Expected behaviour
If the website does truly use the css file then I feel that it should be able to access it, although I feel that this could be redundant as I am yet to find a broken style in the docs to prove that the css is not being used.

Screenshots
Added above

Desktop (please complete the following information):

  • OS: macOS 10.14.4 (18E226) (latest)
  • Browser Safari
  • Version (Version 12.1 (14607.1.40.1.4))

Cheat sheet

I think having a single page of all available queries and methods with short descriptions would be really cool. Something people could open up or even print and use as a reference. Anyone want to build that?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.