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

Moving JsonSchemas into this repo #613

Merged
merged 52 commits into from
Nov 3, 2022
Merged

Conversation

olemartinorg
Copy link
Contributor

Description

Currently there are multiple open PRs in the CDN repo, and these 'never' seem to be merged, and most don't have privileges to merge them. Adding to that, functionality (most often implemented in this repo first) is what makes changes to these schemas necessary. Because of this, moving the schemas here is obviously better - and we can roll out changes to them at the exact same time as we release new versions of app-frontend.

Of note here:

Related Issue(s)

Verification

  • Your code builds clean without any errors or warnings
  • Manual testing done (required)
  • Relevant automated test added (if you find this hard, leave it and we'll help out)
  • All tests run green

Documentation

  • [ ] User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

lorang92 and others added 30 commits November 18, 2020 12:34
Co-authored-by: Kylstad <acn-nkyls@ai-dev.no>
* add message widget

* test with multiple widgets

* update message text key

* update widgets

* widget updates

* update layout schema with new component type

* update schema for attachment list component

* updated after pr comments
Added schemas for layout
* Added new trigger + triggers on page level on json schemas

* Added title

Co-authored-by: EKEBERG Steffen <steffen.ekeberg@soprasteria.com>
* Added new trigger + triggers on page level on json schemas

* Added title

Co-authored-by: EKEBERG Steffen <steffen.ekeberg@soprasteria.com>
* Add formatting property for input component.

* number format schema

* test number-format schema

* fix misplaced elements

* update required condition

* add missing newline

* update conditional required

* test new condition

* test updated schema

* working schemas

* add default values
Added schemas for layout
* Add formatting property for input component.

* number format schema

* test number-format schema

* fix misplaced elements

* update required condition

* add missing newline

* update conditional required

* test new condition

* test updated schema

* working schemas

* add default values
* Add JSON schema pattern for layout.id
* Specify that groupComponents.children, needs to be unique

Altinn studio designer crashes if there are duplicate entries in groupComponents.children. It will be much easier to catch if VSCode complains.

* Clarify help text
* Added image in schema-validator

* Correction acc. to comments
* Add explanation of the keyword 'today'

* Update schemas/json/layout/layout.schema.v1.json

Co-authored-by: Steffen Lorang Ekeberg <steffen.ekeberg@gmail.com>

* Fix description after feedback on PR

* Remove extra quote character

Co-authored-by: Steffen Lorang Ekeberg <steffen.ekeberg@gmail.com>
* Added tableHeaders to json schema
* Added Json schema for labelGrid

Altinn/altinn-studio#7027

* Update schemas/json/layout/layout.schema.v1.json

Co-authored-by: Steffen Lorang Ekeberg <steffen.ekeberg@gmail.com>

* Fix indentation levels in layout.schema.v1.json.

Co-authored-by: Steffen Lorang Ekeberg <steffen.ekeberg@gmail.com>
* Update schemas/json/layout/layout.schema.v1.json

Co-authored-by: Terje Holene <terje.holene@gmail.com>
Co-authored-by: EKEBERG Steffen <steffen.ekeberg@soprasteria.com>
Co-authored-by: EKEBERG Steffen <steffen.ekeberg@soprasteria.com>
…amp for date picker component (#82)

The implementation actually defaults to 'undefined', and there is a strict check if the timestamp is set to 'false'.
The result of this check (timestamp === false) will only be true if timestamp is 'false'. 'undefined' (default) will not result in this check evaluating to 'true'.
@olemartinorg olemartinorg linked an issue Nov 2, 2022 that may be closed by this pull request
@sonarqubecloud
Copy link

sonarqubecloud bot commented Nov 2, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@olemartinorg olemartinorg requested a review from tjololo November 2, 2022 22:29
Copy link
Contributor

@Magnusrm Magnusrm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! Looks good to me 👍

Copy link
Member

@bjosttveit bjosttveit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very good!

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 this pull request may close these issues.

Move the layout schema(s) to this repo