Eirik Mikkelsen
Eirik Mikkelsen
@mjulstein I guess we should not point our devs to a domain we don't control. Seems risky, an unneccesary attack vector. The obvious and "correct" solution is to use `local.altinn.studio`...
> This is a project that is slowly becoming somewhat of a standard for new .Net core applications. There are some good stuff (test and src at root), and some...
And perhaps we finally should extract our "perfect .net core app template" into a seperate repo? :)
> Would it be better to have a standard way of handling messages Currently the inbox is based on the very limited service types in Altinn 2, something that makes...
Hopefully one does not create apps that only shows the same content. Seems like a strange thing to do?
Both Gitea and LibGit2Sharp has been updated to latest. Closing this issue.
Seems like this feature allready has been added by Bert in the [Dinish fork](https://github.com/playbeing/dinish). See discussion in issue numero #1.
@lvbachmann Hadde en diskusjon med Khurram hos SKD, og de har et behov som strekker seg ut over kun branching i Studio, men det å også kunne deploye og teste...
Also see this comment https://github.com/Altinn/altinn-studio/issues/5494#issuecomment-1864027347 This issue basically boils down to if it's ok for Studio as a product to have potential misleading buttons for apps in Altinn inbox until...
> who exactly is responsible for making changes to altinn 2 inbox for altinn 3 elements @nkylstad In reality, Studio is the only product in Altinn 3 that has elements...