Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
I
iTasks-SDK
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 62
    • Issues 62
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • clean-and-itasks
  • iTasks-SDK
  • Issues
  • #343

Closed
Open
Opened Sep 18, 2019 by Steffen Michels@smichels
  • Report abuse
  • New issue
Report abuse New issue

constraints on values of controls are only checked on client

For instance, the generic editor for String requires a minimal length of 1. However, the editor has a valid state if initialised with the empty string:

updateInformation [] "" >&> viewSharedInformation [ViewAs isJust]

@baslijns , it doesn't have priority for me, but I assign it to you to make sure that this is considered in the new editor design.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
Bug
Assign labels
  • View project labels
Reference: clean-and-itasks/iTasks-SDK#343