Datasources - part 4: documentation #3105
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rolnico
changed the title
flo-dup
force-pushed
the
nro/datasources_3_new_features
branch
from
47bf1a7
to
2a4ba27
Compare
Signed-off-by: Nicolas Rol <nicolas.rol@rte-france.com>
flo-dup
force-pushed
the
nro/datasources_4_documentation
branch
from
8916995
to
86fd669
Compare
Signed-off-by: Florian Dupuy <florian.dupuy@rte-france.com>
flo-dup
reviewed
Aug 9, 2024
docs/index.md
Outdated
| @@ -22,6 +22,7 @@ grid_model/index.md | |||
| grid_features/index.md | |||
| simulation/index | |||
| data/timeseries | |||
| data/datasources | |||
There was a problem hiding this comment.
I think this should be deeper in the index, it's more for developers or expert users. Maybe a "going further" section in grid exchange formats
|
Signed-off-by: Nicolas Rol <nicolas.rol@rte-france.com>
rolnico
changed the title
Signed-off-by: Nicolas Rol <nicolas.rol@rte-france.com>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
Other information: