-
Notifications
You must be signed in to change notification settings - Fork 532
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added required attribute to textArea. #501
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @Decipher and thank you for your PR.
Can you please remove dist files and package-lock from it ?
They will be generated in the next release.
once the dist files are removed, I'll approve this PR |
I'll make that change shortly. Out of curiosity, is there an easy way for me to use my fork with the dist files until a release has this change? That's the main reason I committed those files, as I have a client who requires that change in a production site. |
My production project is based on my fork, just tell package.json to point to your github fork as the repo for it - can provide a sample tomorrow if you need one. Readup on package.json and Git repos option. |
@zoul0813 I meant, because I have to remove the dist files for the PR, but I need the built dist files for me client, what the recommended approach there was. It's all sorted now, I simply made a branch with the dist files and removed the dist files from this branch, and then pointed the package.json at the branch with the dist files. It just feels a little weird to me, but seems to get the job done. |
@Decipher Thank you for your work ! |
…o v3 * 'v3' of github.com:vue-generators/vue-form-generator: Bump version to 3.0.0-beta.7 - Update dependencies - Export dist files Single export - No more core vs full since both are the same right now - Optionnal fields will be removed from it in future update Clean useless folders Update submodule dev Custom legend block for group - Possibility to use scoped-slot to customise fully how legend is build - Expose `group` and `groupLegend` in slot prop vue-generators#509 vue-generators#522 vue-generators#521 vue-generators#501 Fix deep property path not working
Bug? / Feature request.
If you use the
required
attribute for atextArea
you'll get a required label but no HTML 5 validation, e.g., the form will submit even though it looks to be required.The HTML5
required
attribute will be applied to the text area.No?
Unsure of the exact process for developing against this project, so can't confirm this PR is done as required.