I2D System
Script para descargar los boletines judiciales en México.
An update to teacher's archaic HTML page for form elements
Platform to share your dreams
Videojuego que busca ayudar a los niños a aprender sobre la higiene
School project that consists of a jeopardy for teachers to use in their classes
PatoBeltran/metodos-numericos 1
Repositorio que albergara una cantidad de métodos numéricos que serán realizados como parte del curso "Métodos numéricos en la Ingeniería".
Site for trying to give information of political candidates to citizens
Repositorio de Buzón Legal
Web APP Roady
push eventsamstarling/formik
commit sha 1e5e9a04803c4820d5eb271de0628181fcbb04c3
Add code unintentionally deleted
push time in 9 days
push eventsamstarling/formik
commit sha 5f6a88b093bc444235026aa34e1a3002b29f78ca
Resolve values outside reducer to be able to validate in setValues
push time in 9 days
push eventsamstarling/formik
commit sha a9dee8a7dccbcb9aa38e73305a90063aae6541dc
Fix: return onSubmit promise result in submission (#2420)
commit sha c4368955def9e5f26a89f81382139d1f5b7959c7
Tutorial Final Result fix (#2484)
commit sha f5ce47b1f79a856dfb4df650a7018b3f09d15c92
fix: Update innerRef type signature (#2325)
commit sha 1c94eea9f839f87927a3bcebfb088c100a24b3ee
Fix handleChange / handleBlur typings (#2472) Co-authored-by: hastom <aklyavlin@onvis.ru>
commit sha 6535e4ca8039695ecc52221f8bc55929bebd7f03
Update README.md (#2492) Add a multistep wizard example.
commit sha 926577f1b2aaf1f249d77b4887405d3a408580d1
Update field.md (#2460) minor docs fix. *Question*: the quotation section on line 30 says that "`component` ... props could also be used for rendering.". But we are actually saying that <Field component> is valid. This seems ... confusing. Is it that `render` is now deprecated but `component` is not, or is the use of `component` here different than `<Field component>` ?
commit sha 30269b42603e6e6d3bac80b1cf767f88a7ec314b
add "avoid nesting" section (#2459) for people who want to have properties with dots in its name
commit sha 918fa9574a18217cf625f35160c83a9ff476ef5d
Fix peer dependency version (#2451)
commit sha 9712c2df6ab182d28bdafd99f35abb2f3a86073d
BLM
commit sha 849ed497e24afbc1c9d41dbd0ad84db8231a48c2
Remove period
commit sha a9dee79f3138d17cb72e7bc905691dab143b6af8
Update LICENSE
commit sha e6383ac75c20cc462fb11be2c9188261ab668f6a
Fix validation.md (#2555) Example code https://jaredpalmer.com/formik/docs/guides/validation#manually-triggering-validation In the example this line breaks the code because of additional parentheses was added at the end <button type="button" onClick={() => validateForm().then(() => console.log('blah')))}> It should be <button type="button" onClick={() => validateForm().then(() => console.log('blah'))}>
push time in 9 days
PR opened formik/formik
This is a continuation of https://github.com/formik/formik/pull/1513 which was closed for inactivity. This PR has addressed all the comments and reused React.SetStateAction types.
With this, formik consumers could pass a value or a function to setValues just like you can with React's setState dispatchers.
pr created time in 9 days
pull request commentjaredpalmer/formik
@jaredpalmer should I try to open a new PR to get traction on this functional updates with setValues feature or can we just reopen this one since the comments have already been addressed?
comment created time in 19 days
pull request commentjaredpalmer/formik
Hey @jaredpalmer I updated the branch for this PR with latest master and refactored to use React.SetStateAction as the type instead of creating a new one. Can we reopen this PR? It would be nice to see this in the next formik's release.
comment created time in a month
push eventsamstarling/formik
commit sha b36725e2f525abb8ea0a7be5211dc47b8482862d
Add checkbox and async submit examples to storybook
commit sha 4b4f04b88cf073c7cf08dbf9ce4e6a673c7b07a4
Fix invariant in useFormikContext (#1720)
commit sha 33a58150ac5582fe782d8d62f13f92f8c4d8a514
Merge branch 'master' of github.com:jaredpalmer/formik
commit sha 5f9464676797559d2a8f3f24d3fe18a78a8528dc
Add Related section with mention of TSDX (#1709)
commit sha 0a7950042f772b7249ece3fb8b12e1c52ca4eb50
Update Gusto logo (#1705)
commit sha dce8d31bb07daf0c28c24837c47e629b3aad9cfa
Bump prettier and run it on docs (#1701)
commit sha 98fe4e39e9d4fa2a5a59c552ea75404eb6080c36
Update typescript.md (#1753) SFC is deprecated
commit sha 6e098e33a13b7a19a7e4588ce41b22268b53321c
Switch to GitHub CI (#1758) * Add basic Node CI workflow * Add docs workflow * Skip checking out code in docs ping? * Update on: format * Test filter * Try nesting * See what is in github context * Try to only run doc deploy on master * Try putting quotes around master * Single quotes? * Remove CircleCI code * Remove circle badge from readme
commit sha bd0d5995d7b0db92aaf3c69c74ea740c00c1a4e8
Fix useEventCallback() (#1763)
commit sha 6feeb32237b7dcd328197a0b233e298327854203
v2.0.1-rc.13
commit sha 283228244f25a9f700425d2f679e845dcf3ab7a4
Use useIsomorphicLayoutEffect (#1766)
commit sha 6d8e56de84380e7a3d2322a690dad6ba6e8e9199
Kill cached directories
commit sha 24ac8ddbddc5717c57178b8a9e90f752fbaa6858
Fix undefined error in yupToFormErrors. (#1767) This should resolve #903, #1486, and possibly others.
commit sha 3da4858c971d4789f0669aba2b6ba83b2f0ba385
Document useFormikContext() (#1764) * Document useFormikContext * Add to docs sidebar
commit sha da9da04f921d44bf9cca330e55feec0a1c157427
Update validation.md (#1769)
commit sha 0b246136e265eef094f704a528d35e41341fc527
fix setIn when deep object or array is wrong type (#1774)
commit sha 26ce764460ac0d646dde2e7021caeca4ed6bfe72
add zauberware.com as formik user (#1710)
commit sha 44afb37ab6af73011ef4a0b10577d56cc5a01be9
Release Notes for Latest Version in Docs (#1785)
commit sha 2be1cf0ef48dfa3d8c269e1753572608f226af17
Update tutorial.md (#1806)
commit sha eefe9647a150ca2f861d3cd79b3c758cfc02fe17
Create FUNDING.yml
push time in a month
push eventsamstarling/formik
commit sha b36725e2f525abb8ea0a7be5211dc47b8482862d
Add checkbox and async submit examples to storybook
commit sha 4b4f04b88cf073c7cf08dbf9ce4e6a673c7b07a4
Fix invariant in useFormikContext (#1720)
commit sha 33a58150ac5582fe782d8d62f13f92f8c4d8a514
Merge branch 'master' of github.com:jaredpalmer/formik
commit sha 5f9464676797559d2a8f3f24d3fe18a78a8528dc
Add Related section with mention of TSDX (#1709)
commit sha 0a7950042f772b7249ece3fb8b12e1c52ca4eb50
Update Gusto logo (#1705)
commit sha dce8d31bb07daf0c28c24837c47e629b3aad9cfa
Bump prettier and run it on docs (#1701)
commit sha 98fe4e39e9d4fa2a5a59c552ea75404eb6080c36
Update typescript.md (#1753) SFC is deprecated
commit sha 6e098e33a13b7a19a7e4588ce41b22268b53321c
Switch to GitHub CI (#1758) * Add basic Node CI workflow * Add docs workflow * Skip checking out code in docs ping? * Update on: format * Test filter * Try nesting * See what is in github context * Try to only run doc deploy on master * Try putting quotes around master * Single quotes? * Remove CircleCI code * Remove circle badge from readme
commit sha bd0d5995d7b0db92aaf3c69c74ea740c00c1a4e8
Fix useEventCallback() (#1763)
commit sha 6feeb32237b7dcd328197a0b233e298327854203
v2.0.1-rc.13
commit sha 283228244f25a9f700425d2f679e845dcf3ab7a4
Use useIsomorphicLayoutEffect (#1766)
commit sha 6d8e56de84380e7a3d2322a690dad6ba6e8e9199
Kill cached directories
commit sha 24ac8ddbddc5717c57178b8a9e90f752fbaa6858
Fix undefined error in yupToFormErrors. (#1767) This should resolve #903, #1486, and possibly others.
commit sha 3da4858c971d4789f0669aba2b6ba83b2f0ba385
Document useFormikContext() (#1764) * Document useFormikContext * Add to docs sidebar
commit sha da9da04f921d44bf9cca330e55feec0a1c157427
Update validation.md (#1769)
commit sha 0b246136e265eef094f704a528d35e41341fc527
fix setIn when deep object or array is wrong type (#1774)
commit sha 26ce764460ac0d646dde2e7021caeca4ed6bfe72
add zauberware.com as formik user (#1710)
commit sha 44afb37ab6af73011ef4a0b10577d56cc5a01be9
Release Notes for Latest Version in Docs (#1785)
commit sha 2be1cf0ef48dfa3d8c269e1753572608f226af17
Update tutorial.md (#1806)
commit sha eefe9647a150ca2f861d3cd79b3c758cfc02fe17
Create FUNDING.yml
push time in a month
issue commentmicrosoft/fluentui
Will this version support the use of ReactDOMServer.renderToNodeStream(element) for server side rendering?
comment created time in a month
startedFullHuman/purgecss
started time in a month
created tagAzure/iot-ux-fluent-controls
A collection of shared react UI components used across IoT teams.
created time in a month
push eventAzure/iot-ux-fluent-controls
commit sha af435f5ac58c5bb2f6f85791dbb9f56d1f1e4a7e
Add dropshadow to searchbar (#195)
push time in a month
PR merged Azure/iot-ux-fluent-controls
In an effort to make white labeled more accessible in every possible masthead color selection it was decided to add a dropshadow to the search bar to make it have more contrast to the masthead background.
This follows the practice that office uses on their search bar and here are some examples of how it looks on different backgrounds:
pr closed time in a month
PR opened Azure/iot-ux-fluent-controls
In an effort to make white labeled more accessible in every possible masthead color selection it was decided to add a dropshadow to the search bar to make it have more contrast to the masthead background.
This follows the practice that office uses on their search bar and here are some examples of how it looks on different backgrounds:
pr created time in a month
created tagAzure/iot-ux-fluent-css
A minimal set of styles, themes and colors that are standardized across the Azure IoT organization.
created time in a month
push eventAzure/iot-ux-fluent-css
commit sha 05c8ef5c8e144c3e4847526f7b8f591555c60eeb
Update colors to fix a11y (#41)
push time in a month
push eventAzure/iot-ux-fluent-css
commit sha 4017b8a6767c34be63a60d0791160e8eea42c505
added color content background featured colors
commit sha 3381ea87eaa9df86855c44606907fb04e3ce5380
Merge pull request #39 from Azure/rl/featured-color added color content background featured colors
commit sha 0b5e647840cb23c617b06862e1667685d74d4204
update changelog and package version
commit sha 833b227c1658896d8fa0ab55fdeb9d502623a27c
Merge branch 'master' of https://github.com/Azure/iot-ux-fluent-css into rl/featured-color
commit sha eb2fcdc6847fea2ad210afd6ed1df1673a0fd348
Merge pull request #40 from Azure/rl/featured-color Update package version number and changelog
commit sha 1fac607179331828cf6f967d39aeb0ed1eae8141
Update colors to fix a11y
push time in a month
issue commentGoogleChrome/lighthouse
Update yargs-parser dependency
@patrickhulce does v6.0.0 also fixes the transitive dependency of chrome-launcher using an old version of mkdirp?
comment created time in 2 months
issue commentGoogleChrome/lighthouse
Update yargs-parser dependency
You are right, I messed up, the lighthouse version I use is 5.6.0 the yargs-parser was the one that was 7.0.0 but needed to be updated. My bad.
comment created time in 2 months
issue openedGoogleChrome/lighthouse
Environment Information
- Lighthouse version: 7.0.0
Hi, I'm trying to resolve some npm vulnerabilities gotten from npm audit on my project and there are some that are coming from this package.
Low Prototype Pollution
Package minimist
Patched in >=0.2.1 <1.0.0 || >=1.2.3
Dependency of lighthouse
Path lighthouse > chrome-launcher > mkdirp > minimist
More info https://npmjs.com/advisories/1179
Low Prototype Pollution
Package minimist
Patched in >=0.2.1 <1.0.0 || >=1.2.3
Dependency of lighthouse
Path lighthouse > mkdirp > minimist
More info https://npmjs.com/advisories/1179
Low Prototype Pollution
Package yargs-parser
Patched in >=13.1.2 <14.0.0 || >=15.0.1 <16.0.0 || >=18.1.2
Dependency of lighthouse
Path lighthouse > yargs-parser
More info https://npmjs.com/advisories/1500
I've been looking and your dependency tree and it seems like you are locked into the yargs-parser version, you use a legacy version of mkdirp and chrome-launcher seems to use this same version. I want to remove this vulnerabilities but I don't want to update this packages and have them break your usages. What is your guidance to fix this issue?
created time in 2 months
startedcodetunez/mock-devices
started time in 2 months
created tagAzure/iot-ux-fluent-controls
A collection of shared react UI components used across IoT teams.
created time in 3 months
push eventAzure/iot-ux-fluent-controls
commit sha 67395d48ad235b758b09f5284e630c7f12377e52
Update css library and minor style fixes (#192)
push time in 3 months
PR merged Azure/iot-ux-fluent-controls
Updated the version of css library that brings in some new link colors and updated the usage of them in this library.
Also fixed an issue with input where the placeholder was not updated with disabled styles.
pr closed time in 3 months
PR opened Azure/iot-ux-fluent-controls
Updated the version of css library that brings in some new link colors and updated the usage of them in this library.
Also fixed an issue with input where the placeholder was not updated with disabled styles.
pr created time in 3 months
created tagAzure/iot-ux-fluent-css
A minimal set of styles, themes and colors that are standardized across the Azure IoT organization.
created time in 3 months
push eventAzure/iot-ux-fluent-css
commit sha 1df19ce3d15425896ba331381a806e20b7a75bd5
Fix dark mode colors and add link colors (#38)
push time in 3 months
PR merged Azure/iot-ux-fluent-css
Made changes based on team's and design feedback:
- Foreground disabled, selected hover and foreground inactive in dark to have better contrast
- Added separate colors for links to not use accent color and modified normalize to use them
- Add underline to pressed state of links
pr closed time in 3 months
push eventAzure/iot-ux-fluent-css
commit sha b0522ddb23f0999e50ecc9c355500a226c085902
Fix typo
push time in 3 months
issue openedmicrosoft/fluentui
CommandBar doesn't resize properly when animation present
Environment Information
- Package version(s): 7.76.2
Please provide a reproduction of the bug in a codepen:
https://codepen.io/PatoBeltran/pen/xxGvRWV?editors=0110
Actual behavior:
When an element with an animation pushes the container of the CommandBar to be smaller, the component doesn't react properly and pushes element outside of the width of the container. Notice that having the same component without the animation does resize properly (it seems like the component is reading the size to early)
If you look in the codepen when you switch the variable WITH_ANIMATION to false, the command bar will resize properly upon opening the sidebar.
Expected behavior:
The commad bar should resize properly even if the size is modified by an animation.
Priorities and help requested:
Requested priority: High Products/sites affected: IoT Central
created time in 3 months
issue commentmicrosoft/fluentui
Command bar doesn't resize properly when on a flex child with flex-grow
Also, I noticed that the ms-OverflowSet ms-CommandBar-primaryCommand is using this same technique to size it's content... therefore if this is the issue, that container should also include a min-width: 0 to make sure flex is not making this container bigger than it should.
comment created time in 3 months
issue commentmicrosoft/fluentui
Command bar doesn't resize properly when on a flex child with flex-grow
hey @aneeshack4, thanks for your answer... while I agree with you about this behavior of flex-grow, I find it a bit weird that the component knows to resize a couple of times but then stops. If the issue was purely how flex-box handles sizing, wouldn't the action bar component never put element's in overflow because the size would never be smaller than all the items?
comment created time in 3 months