Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
I
iTasks-SDK
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 73
    • Issues 73
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 6
    • Merge Requests 6
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • clean-and-itasks
  • iTasks-SDK
  • Issues
  • #250

Closed
Open
Opened Sep 10, 2018 by Steffen Michels@smichelsMaintainer

optional (Maybe) editors

Currently, editors in an invalid state within a Maybe editor are valid and produce a Nothing value. The concept of editors should be changed to include three possible states:

  • valid state (e.g. an integer field with "3")
  • invalid state (e.g. an integer field with "a")
  • empty state (e.g. an integer field with "", this should only be given if the editor was generated with the optional flag)

Complex editor, e.g. for records, should generate a checkbox to indicate that they are empty.

Proposal for new types:

:: Editor = {
...
valueFromState :: !EditState -> *EditorValue a
}

:: EditorValue a = ValidValue a | InvalidValue | EmptyValue
Edited Nov 06, 2020 by Steffen Michels
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: clean-and-itasks/iTasks-SDK#250