Skip to content
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

Move technical sections from domain specific questions to separate section in form1 #369

Open
4 of 6 tasks
blcham opened this issue Oct 9, 2024 · 0 comments · May be fixed by #370
Open
4 of 6 tasks

Move technical sections from domain specific questions to separate section in form1 #369

blcham opened this issue Oct 9, 2024 · 0 comments · May be fixed by #370
Assignees

Comments

@blcham
Copy link
Collaborator

blcham commented Oct 9, 2024

Move technical sections from domain specific questions to separate section in form1, then refactor so it is similar other well processed sections within form1.json.

The following questions should be moved:

  • TTL/SPARQL questions:
    image
  • Date and time-related questions:
    image
  • TODO @blcham: Finishing up with existing questions from the storybook component and existing forms:
    image

The final structure should be:

Layout options
Conditional logic
Input types
    Date and time
        ?! Calendar Component
           ?! Date 
           ?! Time
           ?! Date with time
           ?! Timestamp
        ?! No Calendar component
            ?! Date pattern
    Technical Languages
        Sparql
        TTL
UFO-based patterns
Domain-specific questions

Note that it is possible to use "?" to annotate questions to describe what they demonstrate:
image

A/C:

  • questions should be within form1.json located in order they appear in the form (hopefully it is done like that for Layout options/Conditional logic/ so it should follow
  • questions are well annotated as within the sections above
  • technical sections are removed from domain-specific questions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants