|
1 | 1 | # OS2Web Data lookup [](https://travis-ci.org/OS2web/os2web_datalookup)
|
| 2 | + |
2 | 3 | ## Install
|
3 | 4 |
|
4 |
| -OS2Web Data lookup provides integration with Danish data lookup services such as Service platformen or Datafordeler. |
5 |
| -Module is available to download via composer. |
6 |
| -``` |
| 5 | +OS2Web Data lookup provides integration with Danish data lookup services such as |
| 6 | +Service platformen or Datafordeler. Module is available to download via |
| 7 | +composer. |
| 8 | + |
| 9 | +```shell |
7 | 10 | composer require os2web/os2web_datalookup
|
8 | 11 | drush en os2web_datalookup
|
9 | 12 | ```
|
10 | 13 |
|
11 | 14 | ## Update
|
12 |
| -Updating process for OS2Web Data lookup module is similar to usual Drupal 8 module. |
13 |
| -Use Composer's built-in command for listing packages that have updates available: |
| 15 | +Updating process for OS2Web Data lookup module is similar to the usual Drupal 8 |
| 16 | +module. Use Composer's built-in command for listing packages that have updates |
| 17 | +available: |
14 | 18 |
|
15 |
| -``` |
| 19 | +```shell |
16 | 20 | composer outdated os2web/os2web_datalookup
|
17 | 21 | ```
|
18 | 22 |
|
19 | 23 | ## Automated testing and code quality
|
| 24 | + |
20 | 25 | See [OS2Web testing and CI information](https://github.com/OS2Web/docs#testing-and-ci)
|
21 | 26 |
|
22 | 27 | ## Contribution
|
23 | 28 |
|
24 | 29 | Project is opened for new features and os course bugfixes.
|
25 |
| -If you have any suggestion or you found a bug in project, you are very welcome |
26 |
| -to create an issue in github repository issue tracker. |
27 |
| -For issue description there is expected that you will provide clear and |
28 |
| -sufficient information about your feature request or bug report. |
| 30 | +If you have any suggestion, or you found a bug in project, you are very welcome |
| 31 | +to create an issue in GitHub repository issue tracker. For issue description, |
| 32 | +there is expected that you will provide clear and sufficient information about |
| 33 | +your feature request or bug report. |
29 | 34 |
|
30 | 35 | ### Code review policy
|
| 36 | + |
31 | 37 | See [OS2Web code review policy](https://github.com/OS2Web/docs#code-review)
|
32 | 38 |
|
33 | 39 | ### Git name convention
|
| 40 | + |
34 | 41 | See [OS2Web git name convention](https://github.com/OS2Web/docs#git-guideline)
|
35 | 42 |
|
36 | 43 | ### Using services in other modules
|
37 | 44 |
|
38 |
| -``` |
| 45 | +```php |
39 | 46 | // CVR lookup
|
40 | 47 | /** @var \Drupal\os2web_datalookup\Plugin\DataLookupManager $pluginManager */
|
41 | 48 | $pluginManager = \Drupal::service('plugin.manager.os2web_datalookup');
|
@@ -68,22 +75,25 @@ if ($cprPlugin->isReady()) {
|
68 | 75 |
|
69 | 76 | ### Datafordeler integration (https://datafordeler.dk)
|
70 | 77 |
|
71 |
| -In scope of os2forms project already implemented light integration |
72 |
| -with Danmarks Adresseregister (DAR) via fetching data for form elements |
73 |
| -autocomplete. See [os2forms_dawa submodule](https://github.com/OS2Forms/os2forms) |
| 78 | +In the scope of os2forms project already implemented light integration with |
| 79 | +Danmarks Adresseregister (DAR) via fetching data for form elements autocomplete. |
| 80 | + |
| 81 | +See [os2forms_dawa submodule](https://github.com/OS2Forms/os2forms) |
74 | 82 |
|
75 | 83 | As soon as it is clear how the integration is going to be used, then
|
76 |
| -os2forms_dawa will be refactored to OS2Web Data lookup plugin plugin. |
| 84 | +os2forms_dawa will be refactored to OS2Web Data lookup plugin. |
77 | 85 |
|
78 | 86 | ## Important notes
|
| 87 | + |
79 | 88 | ### Serviceplatformen plugins
|
80 |
| -Settings for CPR and CVR serviceplantormen plugins are storing as configuration |
81 |
| -in db and will(could) be exported as `yml` file via Drupal configuration |
82 |
| -management system. And afterwards could be tracked by `git`. |
83 | 89 |
|
84 |
| -If case you have public access to your git repository all setting from plugins |
| 90 | +Settings for CPR and CVR serviceplatformen plugins are storing as configuration |
| 91 | +in db and will(could) be exported as `yml` file via Drupal's configuration |
| 92 | +management system. And afterward could be tracked by `git`. |
| 93 | + |
| 94 | +If case you have public access to your git repository, all settings from plugins |
85 | 95 | will be exposed for third persons.
|
86 | 96 |
|
87 |
| -To avoid/prevent this behavior we recommend use `Config ignore` module, where |
88 |
| -you can add all settings you do not want to export/import via configuration |
| 97 | +To avoid/prevent this behavior, we recommend use `Config ignore` module, where |
| 98 | +you can add all settings you do not want to export/import via the configuration |
89 | 99 | management system.
|
0 commit comments