Skip to content
This repository has been archived by the owner on Mar 23, 2023. It is now read-only.

ux: mandatory form fields are not identifiable as such #1738

Closed
dated opened this issue Feb 28, 2020 · 3 comments
Closed

ux: mandatory form fields are not identifiable as such #1738

dated opened this issue Feb 28, 2020 · 3 comments
Labels
Type: Refactor The pull request improves or enhances an existing implementation.
Milestone

Comments

@dated
Copy link
Contributor

dated commented Feb 28, 2020

Currently there is no way to distinguish a mandatory form field from optional form fields.

@ghost
Copy link

ghost commented Feb 28, 2020

Thanks for opening this issue! A maintainer will review this in the next few days and explicitly select labels so you know what's going on.

If no reviewer appears after a week, a reminder will be sent out.

@stale
Copy link

stale bot commented Mar 29, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: Stale The pull request is in need of updates but there has not been a sufficient response. label Mar 29, 2020
@alexbarnsley alexbarnsley added the Type: Refactor The pull request improves or enhances an existing implementation. label Mar 29, 2020
@stale stale bot removed the Status: Stale The pull request is in need of updates but there has not been a sufficient response. label Mar 29, 2020
@faustbrian faustbrian added this to the 3.0.0 milestone May 22, 2020
@faustbrian
Copy link
Contributor

Resolved in v3

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Type: Refactor The pull request improves or enhances an existing implementation.
Projects
None yet
Development

No branches or pull requests

3 participants