PatoBeltran ( Patricio Beltran )

Patricio Beltran PatoBeltran @microsoft Seattle, WA https://www.linkedin.com/in/patriciobeltran UX Software Enginner at Microsoft working on @Azure IoT

repos

gists

followers

following

PatoBeltran/miid 2

I2D System

eleloya/topolegal 1

Script para descargar los boletines judiciales en México.

PatoBeltran/codebotLab 1

An update to teacher's archaic HTML page for form elements

PatoBeltran/dreallow 1

Platform to share your dreams

PatoBeltran/EnoxYPeni 1

Videojuego que busca ayudar a los niños a aprender sobre la higiene

PatoBeltran/jeopardyDAW 1

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".

PatoBeltran/miscandidatos 1

Site for trying to give information of political candidates to citizens

acrogenesis/BuzonLegal 0

Repositorio de Buzón Legal

canalesb93/Roady 0

Web APP Roady

issue commentformium/formik

Manual validation should have a flag to touch all fields

@CristianoYL I've found that there is, if you run formik.setTouched(setNestedObjectValues(errors, true)) where errors is the result of formik.validateForm() you get all the fields touched.... the problem is that you have to do it manually, instead of having an option to do it within validateForm... this is the code I have, which is basically a copy of what handleSubmit inside formik does.

const errors = await form.validateForm();
if (Object.keys(errors).length === 0) {
  // Form is valid, do any success call
} else {
  form.setTouched(setNestedObjectValues<FormikTouched<FormValues>>(errors, true));
}

The problem is that if you want to touch all the fields every time you run manual validation you have to do this code all the time

PatoBeltran

comment created time in 18 days

issue openedformium/formik

Manual validation should have a flag to touch all fields

🚀 Feature request

Current Behavior

When submitting a form today, formik's handleSubmit will run manual validation and then touch all fields to show the validation errors to the user.

If you run manual validation this behavior is not there, you have to manually check the results of the validation and touch all fields using setNestedObjectValues (basically mimic what handleSubmit does)

Desired Behavior

formik's validate form should have a flag that lets the user have the exact same behavior as handleSubmit to avoid having to use setNestedObjectValues every time you trigger manual validation.

Suggested Solution

Adding an optional setTouched?: boolean parameter to validateForm to do this behavior.

I'll be willing to do a PR for this! Let me know if you agree with the approach or if this has been considered but there's a reason not to add it. Thanks!

created time in 20 days

issue commentmicrosoft/vscode-remote-release

Can no longer forward to port 80 as it is in use (apparently)?

I'm facing this same issue with port 443.

I have a server running windows where I have docker and a web app configured to use ssl. I also have a windows client (laptop) that I use to connect with the ssh vscode extension. Using my windows machine, when I forward port 443 it works fine to assign local 443 to remote 443. In my Mac client, however, when I try forwarding port 443 it doesn't allow me (it does the same for any port < 1024) and just asking a random one to forward to remote 443.

In my case, since the app is configured with custom local domains I need it to be 443 in my local as well, which makes it so that I cannot use my Mac to test using this method.

njbmartin

comment created time in 24 days

startedh5bp/Front-end-Developer-Interview-Questions

started time in a month

push eventPatoBeltran/resume

Patricio Beltran

commit sha 8f8c7f3a41657932c2408a96452a836a1fa88a07

Small changes to markdown resume