Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Having a good doc for repository will encourage us to create better code going forward to support other types of repository.
Even the repo upgrade can be its own clean api
Well we have connector developer guide that details the responsibilities.
I have similar thoughts for the exec engine and repository.
You many ask why? If we think ourselves as external developers we will take less shortcuts and make our code mode extensible and clean is my thought.
for instance
Should the create link api enforce the unique constraint on name or the database table should. these are not documented anywhere clearly for someone trying to add a new repo and the recommended practices are nice to have
Attachments
Issue Links
- is a clone of
-
-
- Resolved
-
- is duplicated by
-
-
- Resolved
-
- is related to
-
-
- Open
-