You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When developing on EODAG, parameters names, such as "missionStartDate" are usually hard-typed string, repeated in many places of the code base. Using a constant file would reduce the risk of typo happening when trying to access a given parameter, which value is constant.
Describe the solution you'd like
We could have something like an eodag internal constants file, listing the parameters that are used in EODAG and constant.
The code would import the constants from there.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When developing on EODAG, parameters names, such as "missionStartDate" are usually hard-typed string, repeated in many places of the code base. Using a constant file would reduce the risk of typo happening when trying to access a given parameter, which value is constant.
Describe the solution you'd like
We could have something like an eodag internal constants file, listing the parameters that are used in EODAG and constant.
The code would import the constants from there.
The text was updated successfully, but these errors were encountered: