Skip to content

Commit

Permalink
Merge pull request #33 from ryanaidilp/release/0.6.0
Browse files Browse the repository at this point in the history
feat: prepare release version 0.6.0
  • Loading branch information
ryanaidilp authored Sep 26, 2023
2 parents d134410 + d8acb05 commit a015c5b
Show file tree
Hide file tree
Showing 95 changed files with 6,652 additions and 148 deletions.
6 changes: 5 additions & 1 deletion .github/cspell.json
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,10 @@
"issn",
"infographics",
"Tengah",
"KBLI"
"KBLI",
"Exim",
"SIMDASI",
"Glosarium",
"SDDS"
]
}
5 changes: 2 additions & 3 deletions .github/workflows/coverage.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,6 @@ jobs:
- name: 📦 Install Dependencies
run: |
flutter pub global activate very_good_cli
very_good --analytics false
very_good packages get --recursive
- name: Run Tests
run: |
Expand All @@ -39,18 +38,18 @@ jobs:
- name: Cleaning lcov.info
run: |
lcov --remove ./coverage/lcov.info \
"**/*_interceptor.dart" \
"**/*_serializer.dart" \
"**/*.g.dart" \
"**/service_locator.config.dart" \
"**/*.freezed.dart" \
"**/*_http_module.dart" \
"**/http_client.dart" \
"**/http_module.dart" \
"**/usecase.dart" \
"**/service_locator.dart" \
"**/register_module.dart" \
"**/env.dart" \
"**/*_log_*.dart" \
"**/http_*.dart" \
-o ./coverage/lcov.info
- name: Upload coverage reports to Codecov
uses: codecov/codecov-action@v3
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/main.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -25,4 +25,4 @@ jobs:
with:
flutter_channel: stable
min_coverage: 80
coverage_excludes: "**/*.config.dart **/register_module.dart **/http_*.dart **/*_interceptor.dart **/*_http_module.dart **/*_log_*.dart **/*.g.dart **/*.freezed.dart **/*_serializer.dart **/service_locator.dart **/env.dart **/usecase.dart"
coverage_excludes: "**/*.config.dart **/register_module.dart **/http_*.dart **/*_http_module.dart **/*_log_*.dart **/*.g.dart **/*.freezed.dart **/*_serializer.dart **/service_locator.dart **/env.dart **/usecase.dart"
63 changes: 63 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,69 @@

All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## 0.6.0+12

> 2023-09-26
### What's New?

- **Added** subject category entity.
- **Added** subject category repository contract.
- **Added** use case to get all subject categories.
- **Added** subject category model.
- **Added** subject category remote data source.
- **Added** subject category repository implementation.
- **Added** subject category feature export.
- **Added** subject entity.
- **Added** subject repository contract.
- **Added** use case to get all subjects.
- **Added** subject model.
- **Added** subject remote data source.
- **Added** subject repository implementation.
- **Added** subject feature export.
- **Added** press release entity.
- **Added** press release repository.
- **Added** use cases to get list and detail of press releases.
- **Added** press release model.
- **Added** press release remote data source.
- **Added** press release repository implementation.
- **Added** press release feature export.
- **Added** example pages for subject, subject category, and press release.
- **Added** routes for subject, subject category, and press release.
- **Added** press release card in the example.
- **Added** fixtures for subject category, subject list, and press release.
- **Added** unit tests for subject category use case.
- **Added** unit tests for subject use case.
- **Added** unit tests for press release use case.
- **Added** unit tests for API endpoints.
- **Added** unit tests for data layer of subject category.
- **Added** unit tests for subject remote data source.
- **Added** unit tests for subject repository implementation.
- **Added** unit tests for press release data source.
- **Added** unit tests for press release repository implementation.
- **Refactored** exception classes.
- **Removed** dead code from the repository.
- **Updated** test names and added missing tests for domain and publication models.
- **Renamed** infographic endpoint and added a new endpoint.
- **Added** tests for the static table endpoint.
- **Created** the `StaticTable` entity, repository contract, use case, and model.
- **Optimized** code import and file export.
- **Added** exceptions and failures for the static table feature.
- **Created** a table serializer.
- **Added** tests for the static table model, remote data source, and repository implementation.
- **Integrated** the static table feature into list and view.
- **Updated** static table property documentation.
- **Added** fixtures and tests for static tables.
- **Implemented** unit tests for the static table use case and repository.
- **Added** teardown steps to all unit tests.
- **Fixed** analyzer issues.
- **Fixed** unused page in the example app.
- **Fixed** the UI of the publication example.
- **Fixed** the STADATA exception class to be a normal class.
- **Fixed** exception handling in the HTTP module.

[View Pull Request](https://github.com/ryanaidilp/stadata_flutter_sdk/pull/32)

## 0.5.0+11

> 2023-09-16
Expand Down
11 changes: 11 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,17 @@ Thank you for considering contributing to the Stadata Flutter SDK! Please follow
- Include relevant test cases and documentation for your changes.
- Keep your pull request concise and focused.

## Git Flow

- We use Git Flow as our branching model. Please ensure that your pull requests are based on the appropriate branch, such as `develop` or feature branches.
- Familiarize yourself with the Git Flow process: [Git Flow Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow).

## Signed Commits

- We encourage the use of signed commits to enhance code integrity and traceability.
- Consider using [GPG (GNU Privacy Guard)](https://gnupg.org/) to sign your commits.
- You can learn how to sign commits in [GitHub's documentation](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits).

## Issue Templates

We provide the following issue templates:
Expand Down
Loading

0 comments on commit a015c5b

Please sign in to comment.