-
Notifications
You must be signed in to change notification settings - Fork 3
Initial work #1
Initial work #1
Conversation
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
…astore instance. License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
So the PR is ready for review. I would also ask for the guidance of what next steps should be (ofc after reviews)? I assume something like:
As a community member, I can't do much of these, but I would love to work with you, so you could just hire me and then I could do them! 😉 Blocked by release of async/await versions of
|
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
License: MIT Signed-off-by: Adam Uhlir <uhlir.a@gmail.com>
I have also moved the repo under IPFS org. What kind of teams should be assigned to it? I have added JS Team, but not sure if some others should have access also. Also what about "Lead Maintainer"? I can do it, or if somebody else should be it (because PL guidelines or something), then I don't mind that either. |
Co-Authored-By: dirkmc <dirkmdev@gmail.com>
Co-Authored-By: dirkmc <dirkmdev@gmail.com>
Co-Authored-By: dirkmc <dirkmdev@gmail.com>
|
||
return true | ||
} catch (e) { | ||
log('While checking if repo is initialized error was thrown: ' + e.message) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use explain-error here
Co-Authored-By: dirkmc <dirkmdev@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a ton of kickass work here!! thank you so much @AuHau
Let's get it out of the door. I've made some comments on the README. some are nitpicks others are org structure.
indent_size = 2 | ||
trim_trailing_whitespace = true | ||
insert_final_newline = true | ||
end_of_line = lf |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mind adding this file to .gitignore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well I can, but I think it is a good thing to have around as it unities the code style. I know that for that there is aegir lint
but this integrates directly with IDEs. You don't use it in other projects? I feel like I took it from some other JS package...
For example here: https://github.com/ipfs/js-ipfs/blob/master/.editorconfig
README.md
Outdated
* `options.ignoreLock` (bool, optional) - if true will not lock the repo when applying migrations. Use with caution. | ||
* `options.repoOptions` (object, optional) - options that are passed to migrations, that use them to construct the datastore. (options are the same as for IPFSRepo). | ||
* `options.onProgress` (function, optional) - callback that is called after finishing execution of each migration to report progress. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this for progress bars?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 more :)
Co-Authored-By: David Dias <daviddias.p@gmail.com>
A first draft version of the migration tool, that can be meaningfully feedbacked.
To see how migration looks like, see #2
This PR is written against the async PR's of dependencies (datastores mainly) and hence is blocked by this.
Scope-in
Scope and status of this PR (and package):
Scope-out
Thinks that are not in scope of this PR and will be scope of separate PR to js-ipfs that will integrate this package:
Blocked by
Currently, this depends on async/await refactor of
Problems
If IPFSRepo() is used with custom options (e.g. usingdatastore-level
for key storage backend, instead of defaultdatastore-fs
), this is not propagated to migration. ==> Shouldrepo.options
be propagated throughmigrate()/revert()
to each migration?6dc649b added support for passing options to the migrations