Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Doc Rework] Devel files #1371

Merged
merged 11 commits into from
Sep 7, 2023
Merged

Conversation

mapedraza
Copy link
Collaborator

@mapedraza mapedraza commented May 19, 2023

  • Create devel folder
  • Move to devel folder NorthboundInteractions.postman_collection, architecture.md, contribution.md and northboundinteractions.md
  • Merge development.md, usermanual.md and howto.md into devel/development.md (removing previous files)
  • remove doc/config-basic-example.js
  • rename contribution.md to contribution-guidelines.md

This PR is part of a bigger series #1329

Note: #1369 need to be merged before

@mapedraza mapedraza marked this pull request as draft May 19, 2023 11:34
@mapedraza mapedraza marked this pull request as ready for review September 6, 2023 11:57
@mapedraza mapedraza mentioned this pull request Sep 6, 2023
25 tasks
@fgalan
Copy link
Member

fgalan commented Sep 6, 2023

Some files has been merged/renamed. It would be great to check occurrences of the old names in repo files, in order to fix existing links, references, etc.

doc/admin.md Outdated
Copy link
Member

@fgalan fgalan Sep 6, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actual content changes in the text or just formatting in this file?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably autolinter, just formating

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actual content changes in the text or just formatting in this file?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably autolinter, just formating

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actual content changes in the text or just typo fixing?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo + linter


- _newIoTAInfo_: Object containing all the IoTA Information.

## DB Models (from API document)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are they aligned with last version of api.md?

In my opinion, tables should be simplified to avoid duplication. The Description field is already provided in api.md. Ideally, only two columns: payload and DB field, so clearly show the mapping between them (plus a "Notes" column to be used is some additional note about the mapping is worth to be said).

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in aef1589

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added warning note here: 9390511 and noted here: #1329 (comment)

NTC

@@ -0,0 +1,1932 @@
# Development documentation

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I understand, this file is a merge of several things:

  1. old development.md document
  2. old howto.md document
  3. old usernmanual.md document
  4. new generated content (not sure...)

For reviewing, if would be great if we could tell the mapping between the sections in the ToC and the 4 categories above.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Preface" is not coming from any existing document? Or it has been written from scratch?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right, Preface is brand new section

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It comes from

"dependencies": {

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NTC

Comment on lines +85 to +89
If you plan to use the library in your own IoT Agent, you should read the [Developer Guide](./doc/devel/development.md).
You can also review the [Architecture](./doc/devel/architecture.md) documentation and
[Northbound API](./doc/devel/northbound-api.md).

- Details of the architecture of an IoT Agent be found [here](doc/architecture.md).
- Further Advanced topics can be found [here](doc/advanced-topics.md).
- The following features are listed as [deprecated](doc/deprecated.md).
The following features are listed as [deprecated](doc/deprecated.md).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comparing old and new links... this means that old advanced-topics.md is the new nortbound-api.md?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No. advanced-topics.md is embeded into api.md, already present there. As this part of the doc is intended to address readers (both users and developers) to the most interesting files for them, I included api.md for end users, and development.md, architecture.md and northbound-api.md for developers users.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NTC

doc/api.md Outdated
@@ -186,7 +186,7 @@ Some transformation plugins also allow the use of the following optional fields:
be defined as expressions, using the [Expression Language definition](#expression-language-support).
- **entity_type**: configures the type of an alternative entity.
- **reverse**: add bidirectionality expressions to the attribute. See the **bidirectionality** transformation plugin
in the [Data Mapping Plugins section](development.md#bidirectionality-plugin-bidirectional) for details.
in the [Data Mapping Plugins section](.devel/development.md#bidirectionality-plugin-bidirectional) for details.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bidirectional plugin is deprecated. This reserve bullet should be removed (along with the #bidirectionally-plugin-bidirectional section in the development.md file, if already there).

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done here: 8fe383d
And noted here: #1329 (comment)

| `attributes` | `attributes` | |
| `static_attributes` | `staticAttributes` | |
| `internal_attributes` | `internalAttributes` | |
| `expressionLanguage` | `expresionLanguage` | _Removed_ |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| `expressionLanguage` | `expresionLanguage` | _Removed_ |

Given it its decreated functionality and acccoring to https://github.com/telefonicaid/iotagent-node-lib/blob/master/doc/deprecated.md

Documentation on deprecated features is removed from the repository documentation.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this case, it is better to do in a subsequent PR. Noted here: #1329 (comment)
NTC

| `commands` | `commands` | |
| `internal_attributes` | `internalAttributes` | List of internal attributes with free format for specific IoT Agent configuration. I.E:LWM2M mappings from object URIs to attributes |
| `static_attributes` | `staticAttributes` | |
| `expressionLanguage` | `expresionLanguage` | _Removed_ |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| `expressionLanguage` | `expresionLanguage` | _Removed_ |

Idem

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this case, it is better to do in a subsequent PR. Noted here: #1329 (comment)
NTC

mapedraza

This comment was marked as duplicate.

Copy link
Member

@fgalan fgalan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@fgalan fgalan merged commit 2559ca7 into task/doc-rework Sep 7, 2023
@fgalan fgalan deleted the task/doc-rework-development branch September 7, 2023 09:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants