Bootstrap validation conflicts

Question

I am using Vue.js and Bootstrap to design a website. I have a form that I am trying to run my custom validation on. It works fine until the user clicks submit which adds the was-validated class to the form per the bootstrap documentation.

At this point any required input field that has any input whether it meets my custom validation or not is marked as valid and gets a green border and check mark. My custom validation is still being run and displaying b-form-invalid-feedback correctly. However, it seems that was-validated is marking fields with the required prop as valid while not taking my custom validation into account this is leading to conflicting validation as a field has a green check mark (because it satisfies the required property) but still an error message because it is not yet valid per my custom validation.

I have tried removing the :valid style this isn't the effect I want as I do want it to display those styles when it is valid per my validation. Hope this makes sense if not I will provide pictures. I also have a second issue I have a date picker that is not displaying b-form-invalid-feedback at all even when was-validated is added.

My Code


  
    Name
    
    
      You must enter a name
    
  

  
    Choose a date
    
    
      You must enter a valid date
    
  

  
    Service Provided
    
    
      You must enter the service provided
    
  

  
    Email
    
    
      You must enter the part of your email that comes before the '@' symbol
    
  

  
    Domain
    
      
      
        You must enter the part of your email that comes after the '@' symbol
      
    
  

  
    Describe Your Experience
    
    
      You must enter a description of your experience
    
  

  Save

computed: {
        emailStateValidation() {
            if (this.email) {
                return this.emailIsValid() ? true : false;
            }
            return null;
        },
        domainStateValidation() {
            if (this.domain) {
                return this.domainIsValid() ? true : false;
            }
            return null;
        },
    },
    methods: {
        emailIsValid() {
            let regEx = /^(?!.*@)((^[^\.])[a-z0-9\.!#$%&'*+\-/=?^_`{|}~"]*)*([^\.]$)/;
            return regEx.test(this.email);
        },
        domainIsValid() {
            let regEx = /(($$[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}$$)|(([a-zA-Z\-0-9]+\.)+[a-zA-Z]{2,}))$/;
            return regEx.test(this.domain);
        },
        isStateValid(variable) {
            if (variable) {
                return variable.length > 0 ? true : false;
            }
            return null;
        },
        addReview() {
            let mainForm = document.getElementsByName("review-form")[0];
            mainForm.classList.add("was-validated");
        ...

Questions

Resolve the conflict between required and my custom validation causing input fields being prematurely marked as valid
Display b-form-invalid-feedback on datepicker on form submit if date is not selected

user_1887854 · Answer

In a nutshell, remove novalidate from

in your Vue template. When you set novalidate, the inputs will remain in their :valid state throughout their lifecycle until you explicitly call setCustomValidity. Working Sandbox

Since, Bootstrap styles also apply to :valid or :invalid states so, even if your custom validators determine inputs to be invalid, both valid and invalid styles will get applied i.e. :valid and .is-invalid but, I guess it's just happens so, that :valid styles take precedence the way Bootstrap stylesheet is currently written.

U̶s̶e̶ ̶̶n̶o̶v̶a̶l̶i̶d̶a̶t̶e̶̶ ̶w̶h̶e̶n̶ ̶y̶o̶u̶'̶r̶e̶ ̶i̶m̶p̶l̶e̶m̶e̶n̶t̶i̶n̶g̶ ̶a̶ ̶c̶o̶m̶p̶l̶e̶t̶e̶ ̶v̶a̶l̶i̶d̶a̶t̶i̶o̶n̶ ̶s̶o̶l̶u̶t̶i̶o̶n̶ ̶y̶o̶u̶r̶s̶e̶l̶f̶ ̶i̶n̶c̶l̶u̶d̶i̶n̶g̶ ̶̶r̶e̶q̶u̶i̶r̶e̶d̶̶ ̶v̶a̶l̶i̶d̶a̶t̶o̶r̶.̶

With Bootstrap, since it also applies styles to :valid or :invalid states of input, you're better off NOT using novalidate.

Ofcourse, this will enable browser popups asking for filling certain fields which might be unwanted.

Suggestion: Use validated prop on your form and bind it to your form's state and set it to true in addReview(), it will automatically add was-validated class and you don't need to manipulate the DOM directly.

EDIT: Since removing novalidate enables browser validation, submit event no longer fired on the form and hence, was-validated class is never added to the form. This presented an issue in my original answer because messages and icon were not shown without was-validated. I have modified the sandbox to suggest a fix for that and that is to bind click event to submit button for validation logic and using submit event for stuff that should happen after successful validation.

EDIT for Datepicker: The reason why datepicker never invalidated was because of an issue in isStateValid() method specifically the part:

if(variable) { // "" evaluates to false
   // ...
}

Since "" evaluates to false, it will always return null. The fix for that is in combination with the suggestion above of maintaining validated state for the form. Now, instead of checking if(variable), we check if(this.validated) and if it is true, we simply check the length and return either true or false.

user_5091874 · Answer

Fundamentally was-validated is not bootstrap-vue native, it's browser native, which also has no understanding of :state. If you want to use was-validated you can't use custom validations. If you want to use custom validations. See the suggestion For 2. Which is basically, use another variable to control whether validation should be applied.
From the documentation on bootstrap-vue

When set, adds the aria-required="true" attribute on the component. Required validation needs to be handled by your application

You need to explicitly check that the validation should show, it isn't clear from the documentation what required actually does, but it doesn't affect validation. Which explains why that part isn't working. Personally I set a global this.showValidations = true on submit, so that the validations actually run at the right time and not before (and after when expected). In your case, you can check for the was-validated class that you are adding explicitly. It isn't great, but it seems it must be done here.

Bootstrap validation conflicts

2 Answers