AnyFixture will create once instance of a factory for reuse in a number of specs.
This will work fine until we require a clean slate for a specific example.
As we have numerous tests that test like the database is empty,
we get a number of disadvantages:
- After an example with `with_clean_fixture` metadata, the fixture will only be regenerated
after the next example that uses it. This means the order of execution will change
the number of objects in the DB.
- The more `with_clean_fixture` we have, the smaller the performance advantage of AnyFixture will
result in.
- You cannot use an AnyFixture in a spec that needs a clean slate. This should be obvious but was overlooked
by myself.
Updates the copyright to 2021 for all files that have a copyright. Files in our source code without the copyright header still do not receive one automatically. Additionally, backlisted files are also excluded.
Previously the copyright of chiliproject which references redmine stated a copyright of redmine up to and including 2017 which is not true for the code we have in here. Because of that I changed that to 2013
Uses FactoryBot to keep and maintain specific records in a special transaction that does not get removed after each spec.
They automatically are created whenever first hitting them.
This makes an excellent time saver for items that are commonly used, such as an admin user account
When creating a wiki page from the text with, e.g., `[[Foo Bar]]`,
the user gets redirected to wiki#show for a page `foo-bar` (the slug of
the title above).
He thus loses the title attribute he entered previously. Instead we can
pass the title to the new wiki page IFF the page does not exist.
https://community.openproject.com/wp/27462
[ci skip]
Isolated scopes do not inherit from rootScope and thus do not have
`DOUBLE_LEFT_CURLY_BRACE`.
However, every scope has a reference to the rootScope with
`scope.$root` (https://docs.angularjs.org/api/ng/type/$rootScope.Scope)
The description and all other formattable fields are applied to the dom
with `ng-bind-html`. These directives never compile their contents, thus
any escaped expression `{{ ... }}` entered by the user is never evaluated.
We can either:
1. Compile the content needlessly just to remove escaped expressions.
2. Remove the escaped expression explicitly.
This PR implements the second approach.
https://community.openproject.com/work_packages/24050/activity
Eric Schubert