profile
viewpoint
Oriane Daley oriane212 Cambridge, MA orianed.com Front End Dev

oriane212/chart-access 1

Add an accessible, auto-generated fallback to a Chart.js chart.

oriane212/chart-alt 1

Add an accessible, alternative format to your Chart.js chart

oriane212/frogger 1

Star Wars themed frogger game

oriane212/adjds311 0

Color sensor Arduino library

oriane212/animal-trading-card 0

Udacity Front End Dev project

oriane212/carbon 0

A design system built by IBM

oriane212/carbon-website 0

The website for the Carbon Design System.

oriane212/catClicker 0

Javascript Design Patterns course project

oriane212/coffee-map 0

Web app for viewing map of places visited in 'Comedians in Cars Getting Coffee'

startedEbookFoundation/free-programming-books

started time in 14 days

push eventoriane212/my-site

Oriane

commit sha 0558d32aec2c63c506215265fa8545d555f8b768

update intro

view details

push time in 18 days

push eventoriane212/my-site

Oriane

commit sha 21495389a12a74ffda173f894a659f9e031b4fe0

reorder project links

view details

push time in 19 days

startedsmartergiving/free-nonprofit-starter-website

started time in 19 days

push eventoriane212/my-site

Oriane

commit sha 0e6d62200bd9c1e88d086d20311789c05c195c18

update project link to chart-access

view details

push time in 21 days

push eventoriane212/chart-access

Oriane

commit sha f15b0667c205ba9f46b188bd7b8efab13d61d070

v1.1 update with umd

view details

push time in 22 days

push eventoriane212/chart-access

Oriane

commit sha faa4f1419d79fa687003d250f273ab0930faf962

update readme

view details

push time in 22 days

push eventoriane212/chart-access

Oriane

commit sha d8179c811c5d97e060ab1984236262ce5d600d74

v1 with example

view details

push time in 22 days

push eventoriane212/chart-access

Oriane

commit sha 3fa17e8ace6cd6a7614b9d037c86f351feaa30ac

working iife example

view details

push time in 23 days

push eventoriane212/chart-access

Oriane

commit sha 207ae493744421cd6959f6749c1d1c2f6c6a68ee

test generateFBT, addFB for all chart types

view details

push time in 24 days

push eventoriane212/chart-access

Oriane

commit sha e4380b94a87258adb12c8060e0aa800d66aadc84

add rollup-serve, chart.js + types; splitCC, %s fn

view details

push time in a month

push eventoriane212/chart-access

Oriane

commit sha deb69dcd5e991f5a6b195fe10a60ac330835f094

add checkThreshold interface, update fallback

view details

push time in a month

push eventoriane212/chart-access

Oriane

commit sha 663e3e532c31603eb85f83014e9af589f6b58604

add chartConfig interface, barchart; update test

view details

push time in 2 months

push eventoriane212/chart-access

Oriane

commit sha d37c7db0a0901883a8cc1d80b960a8fa88127205

add typescript and jest, first fn w test

view details

push time in 2 months

startedmicrosoft/vscode-recipes

started time in 2 months

startedrollup/awesome

started time in 2 months

push eventoriane212/chart-access

Oriane

commit sha 9407c83b62b7fc4cf42321b86945354a59261136

init setup

view details

push time in 2 months

create barnchoriane212/chart-access

branch : master

created branch time in 2 months

created repositoryoriane212/chart-access

Make a chart accessible

created time in 2 months

startedjwilber/roughViz

started time in 2 months

push eventoriane212/pet-fetch

Oriane Daley

commit sha 027dcb690c9a159cda183eb597f6471fe0d69640

Initial commit

view details

push time in 3 months

create barnchoriane212/pet-fetch

branch : master

created branch time in 3 months

created repositoryoriane212/pet-fetch

Created with CodeSandbox

created time in 3 months

startedsigndict/website

started time in 3 months

PR opened carbon-design-system/carbon-website

fix (tutorial-vue): link in overview

Closes #484

Fixes "developers getting started" link in Tutorial > Vue page.

Changelog

Changed

"developers getting started" link in tutorial/vue/overview.mdx to go to Get started > Develop > Vue tab.

+1 -1

0 comment

1 changed file

pr created time in 3 months

create barnchoriane212/carbon-website

branch : tutorial-vue-link

created branch time in 3 months

fork oriane212/openfoodfacts-server

Open Food Facts database and web interface - 🐪🦋 Perl and JS coders welcome 😊

fork in 3 months

PR opened Terrastories/terrastories

use scrollToPosition List method in Filter event handlers

Hello!

I used the scrollToPosition List method inside StoryList.handleFilter to reset the sidebar scroll position to the top after applying filters and it seems to work as expected.

For the same reset to happen when clearing filters, I added a handleClearFilteredStories to StoryList that runs clearFilteredStories before resetting the sidebar scroll position.

+7 -1

0 comment

1 changed file

pr created time in 3 months

fork oriane212/terrastories

Terrastories is a geostorytelling application built to enable local communities to locate and map their own oral storytelling traditions about places of significant meaning or value to them.

http://terrastories.io

fork in 3 months

startedTerrastories/terrastories

started time in 3 months

startedSheetJS/js-xlsx

started time in 3 months

startedtuvtran/project-based-learning

started time in 3 months

PR opened carbon-design-system/carbon-website

add $inverse-focus-ui token data

Closes # https://github.com/carbon-design-system/carbon-website/issues/481

Hello! Added the $inverse-focus-ui token with data to the Guidelines > Color > Usage page.

Changelog

New

$inverse-focus-ui in color-tokens.js

+21 -0

0 comment

1 changed file

pr created time in 4 months

create barnchoriane212/carbon-website

branch : inverse-focus-ui

created branch time in 4 months

Pull request review commentaamay001/react-resume

add tests for VisibilityChanger

+import React from "react";+import '@testing-library/jest-dom/extend-expect'+import {render, fireEvent} from '@testing-library/react';+import { Provider } from 'react-redux';+import store from '../store';+import VisibilityChanger from "../components/Tools/VisibilityChanger";+import Resume from "../components/Resume";++// TODO: add tests for checking ItemToggleButton[data-testid='showSkillLevel'] button functioning+// TODO: include MoreVisibilityButton within tests++// TODO?: isolate assertions checking for specific tree structures, classes, etc. so that if minor changes are made to how these components render it'll be easier to update tests+++describe(`Toggle buttons render as expected, displayed under "Visibility" with eye icon`, () => {++    test(`Container for toggle buttons renders as expected`, () => {++        const {getByTestId} = render(+            <Provider store={store}><VisibilityChanger/></Provider>+        )+        +        // get root node created by VisibilityChanger+        const vc = getByTestId('VisibilityChanger');++        // should have class "json-resume-tool"+        expect(vc.classList).toContain('json-resume-tool');++        // should contain 14 child elements+        expect(vc.childElementCount).toBe(14);+        +        // first child should be a div with expected classes+        const label = vc.firstChild;+        expect(label.tagName).toBe('DIV');+        expect(label.classList).toContain('ui', 'big', 'basic', 'label');++        // first child should contain 2 nodes (icon and text) with expected attributes and classes+        expect(label.childNodes.length).toEqual(2);+        const [icon, text] = label.childNodes;+        expect(icon.tagName).toBe('I');+        expect(icon.getAttribute('aria-hidden')).toBe("true");+        expect(icon.classList).toContain('eye', 'icon');+        expect(text.nodeName).toBe('#text');++        // text node should have value "Visibility"+        expect(text.nodeValue).toEqual("Visibility");++    })+++    test(`Toggle buttons render as expected`, () => {++        const {getByTestId} = render(+            <Provider store={store}><VisibilityChanger/></Provider>+        )++        /* +            * data-testids for toggle-able resume elements (eg. "Email")+            * each corresponding toggle button has a data-testid = 'show' + the resume element's data-testid, (eg. "showEmail")+        */+        const dataTestIDs = ["Email", "Phone", "Github", "LinkedIn", "Website", "Address", "Certification", "Education", "Experience", "Projects", "TechSkills", "SkillLevel"];+++        dataTestIDs.map(id => {+            // get btn el+            const btn = getByTestId(`show${id}`);++            // expect each button to be a child of the VisibilityChanger container+            expect(btn.parentNode.isSameNode(getByTestId('VisibilityChanger'))).toBeTruthy();++            // expect each button to be a button element and have classlist containing "ui large fluid button"+            expect(btn.tagName).toBe('BUTTON');+            expect(btn.classList).toContain('ui', 'large', 'fluid', 'button');++            // expect it to contain a div with classlist "ui toggle checkbox"+            const div = btn.children[0];+            expect(div.classList).toContain('ui', 'toggle', 'checkbox');++            // expect the div to contain an input with class 'hidden' and type 'checkbox'+            const [input, label] = div.children;+            expect(input.tagName).toBe('INPUT');+            expect(input.classList).toContain('hidden');+            expect(input.getAttribute('type')).toBe('checkbox');++            /* expect the div to also contain a label containing `Show ${id}` */+            expect(label.tagName).toBe('LABEL');++            /// workaround for ids that do not match wording of their labels+            if (id === 'Certification') {+                id = 'Certifications';+            } +            if (id === 'TechSkills'){+                id = 'TechnicalSkills'+            }+    +            let wordsArry = '';+            +            /// ignore 'LinkedIn' when dividing words+            if (id !== 'LinkedIn'){+                wordsArry = id.match(/[A-Z][a-z]+/g);+            } else {+                wordsArry = [id];+            }+            const wordsStr = wordsArry.join(' ');+            expect(label.innerHTML).toBe(`Show ${wordsStr}`);++        })+        +    })+    +})+++describe(`Toggle buttons work as expected`, () => {++    test(`Resume content visibility matches corresponding toggle button status on load`, () => {++        const {getByTestId} = render(+            <Provider store={store}><VisibilityChanger/></Provider>+        )+        const resume = render(<Provider store={store}><Resume/></Provider>);+       +        // note: "showSkillLevel" toggle button not being tested yet+        const dataTestIDs = ["Email", "Phone", "Github", "LinkedIn", "Website", "Address", "Certification", "Education", "Experience", "Projects", "TechSkills"];+        +        dataTestIDs.map(id => {+            // if toggle button status is on by default, corresponding resume content should also be visible+            if(getByTestId(`show${id}`).children[0].classList.contains("checked")) {+                expect(getByTestId(id)).toBeInTheDocument();+            } else {+                // if toggle button status is off by default, corresponding resume content should not be visible+                expect(()=> {+                    getByTestId(id) +                }).toThrow();+            }+        })+            +    })++    test(`Toggle button click updates toggle button status and corresponding resume content visibility`, () => {++        const {getByTestId} = render(+            <Provider store={store}><VisibilityChanger/></Provider>+        )+        const resume = render(<Provider store={store}><Resume/></Provider>);++        // note: "showSkillLevel" toggle button not being tested yet+        const dataTestIDs = ["Email", "Phone", "Github", "LinkedIn", "Website", "Address", "Certification", "Education", "Experience", "Projects", "TechSkills"];+        +        dataTestIDs.map(id => {+            // toggling off should update toggle button status from on to off, and corresponding resume content should disappear+            if(getByTestId(`show${id}`).children[0].classList.contains("checked")) {+                fireEvent.click(getByTestId(`show${id}`));+                expect(getByTestId(`show${id}`).children[0].classList).not.toContain("checked");+                expect(()=> {+                    getByTestId(id) +                }).toThrow();+            } else {+                // toggling on should update toggle button status from off to on, and corresponding resume content should appear+                fireEvent.click(getByTestId(`show${id}`));+                expect(getByTestId(`show${id}`).children[0].classList).toContain("checked");+                expect(getByTestId(id)).toBeInTheDocument();+            }+        })+            +    })+++})+

Should be all set! Thanks

oriane212

comment created time in 4 months

push eventoriane212/react-resume

Oriane

commit sha 087457402f37c9c0e8c128e4bbb6d9989256c615

fix eslint errors in tests

view details

push time in 4 months

startedaamay001/react-resume

started time in 4 months

PR opened aamay001/react-resume

add tests for VisibilityChanger

Hello!

Adding tests for the VisibilityChanger component that check that the expected tree structure gets rendered and that the toggle buttons are displayed and function as expected.

Adding test ids to the VisibilityChanger component, ItemToggleButtons, and corresponding toggleable Resume components.

Adding react-testing-library and jest-dom.

+9902 -3552

0 comment

11 changed files

pr created time in 4 months

create barnchoriane212/react-resume

branch : tests

created branch time in 4 months

startedtwilio-labs/open-pixel-art

started time in 4 months

issue commentfreeCodeCamp/freeCodeCamp

[a11y] Please give the code editor a role on the page

Hi,

I noticed there is a textarea element nested inside the Monaco Editor, and I was able to jump to it using the ‘e’ key, as @frastlin described. I am using Chrome on a Mac. The element has an aria-label, “Editor content; Press Alt+F1 for Accessibility options”, among several other aria attributes.

I initially was going to propose adding an aria-label and/or role for each div containing one of the panels in the layout (ie. instructions, editor, test output, and preview) or wrapping a section around each.

The react-reflex components used for the layout, however, don't seem to support these properties, and the layout seems to break when trying to add a new div or section within the tree.

xnt

comment created time in 4 months

startedcarbon-design-system/carbon

started time in 4 months

create barnchoriane212/carbon

branch : wide-tabs

created branch time in 4 months

create barnchoriane212/first-contributions

branch : add-oriane-d

created branch time in 4 months

startedagauniyal/wireframe

started time in 4 months

startedfreeCodeCamp/freeCodeCamp

started time in 4 months

startedmui-org/material-ui

started time in 4 months

startedprocessing/p5.js

started time in 4 months

startedfacebook/jest

started time in 4 months

more