GitHub-Bitwarden/server - server - Gitea: Git with a cup of tea

Branch: api-integration-tests

Author	SHA1	Message	Date
Justin Baur	231eb84e69	Turn On `ImplicitUsings` (#2079 ) * Turn on ImplicitUsings * Fix formatting * Run linter	4 years ago
Matt Gibson	5537470703	Use sas token for attachment downloads (#1153 ) * Get limited life attachment download URL This change limits url download to a 1min lifetime. This requires moving to a new container to allow for non-public blob access. Clients will have to call GetAttachmentData api function to receive the download URL. For backwards compatibility, attachment URLs are still present, but will not work for attachments stored in non-public access blobs. * Make GlobalSettings interface for testing * Test LocalAttachmentStorageService equivalence * Remove comment * Add missing globalSettings using * Simplify default attachment container * Default to attachments containe for existing methods A new upload method will be made for uploading to attachments-v2. For compatibility for clients which don't use these new methods, we need to still use the old container. The new container will be used only for new uploads * Remove Default MetaData fixture. * Keep attachments container blob-level security for all instances * Close unclosed FileStream * Favor default value for noop services	5 years ago
Kyle Spearrin	29580684a3	upgrade to aspnet core 3.1	6 years ago
Joshua Ford	0f3fcc122d	Add basic Core.Services test files (#526 ) Following the paradigms illustrated in "Working Effectively with Legacy Code", this commit introduces at least one test for each service class implementation. This test is a simple construction test -- we just create each service and assert that it exists. Each test suite includes a comment instructing the developer who comes next to remove the constructor test. We don't want to keep these tests as the codebase matures, as they aren't useful in the longterm. They only prove that we have that class under test. Where test suites failed to construct their associated classes, we skip the test but leave behind the implementation. This is by design, so that as the constructors for those classes change, we are forced to keep the test suite current by leaning on the compiler.	7 years ago