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

Release expressions as default dynamics option #11634

Closed
6 tasks done
Tracked by #10929
standeren opened this issue Nov 20, 2023 · 1 comment
Closed
6 tasks done
Tracked by #10929

Release expressions as default dynamics option #11634

standeren opened this issue Nov 20, 2023 · 1 comment
Labels
kind/user-story Used for issues that describes functionality for our users. solution/studio/designer Issues related to the Altinn Studio Designer solution. status/ready-for-dev Status: Used for issues that are ready for development. Has been through grooming. team/studio

Comments

@standeren
Copy link
Contributor

standeren commented Nov 20, 2023

Description

The new tool for editing expressions in Studio is per now a feature that is enabled when toggling the feature on from the lage-page. The default is the old view for editing the old dynamic-files in gitea. This logic should be switched so the default is the new expression tool.

In addition to this, we should also add a section in the What's new section on the overview page that the new expression tool is the default and that we will remove the possibility to navigate to the old dynamics files from lage-page.

Related issues

Should this also include removing the RuleHandler.js from app template?
Should there also be an issue removing the code (frontend and backend) handling the old dynamics?

  • We have decided to remove the RuleHandler.js file from the app template, making the new editor the default. For apps that already have RuleHandler.js, they will be able to toggle using the old dynamics editor - we therefore need to keep the code for now.

Tasks

Preview Give feedback
  1. framitdavid standeren
  2. added-to-sprint
  3. status/duplicate
  4. 3 of 3
@standeren standeren converted this from a draft issue Nov 20, 2023
@standeren standeren added solution/studio/designer Issues related to the Altinn Studio Designer solution. status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design. team/studio labels Nov 20, 2023
@nkylstad nkylstad added status/ready-for-dev Status: Used for issues that are ready for development. Has been through grooming. kind/user-story Used for issues that describes functionality for our users. and removed status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design. labels Dec 14, 2023
@nkylstad
Copy link
Member

nkylstad commented Oct 8, 2024

Closing as completed

@nkylstad nkylstad closed this as completed Oct 8, 2024
@github-project-automation github-project-automation bot moved this to Documentation in Team Studio Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/user-story Used for issues that describes functionality for our users. solution/studio/designer Issues related to the Altinn Studio Designer solution. status/ready-for-dev Status: Used for issues that are ready for development. Has been through grooming. team/studio
Projects
Archived in project
Development

No branches or pull requests

2 participants