search

mattermost-community / mattermost-plugin-autolink

Automatically rewrite text matching a regular expression into a markdown link.
Apache License 2.0
132 stars 57 forks source link

Add `/autolink import/export` capability #73

Open levb opened 5 years ago

levb commented 5 years ago

If you're interested please comment here and come join our "Contributors" community channel on our daily build server, where you can discuss questions with community members and the Mattermost core team. For technical advice or questions, please join our "Plugin: Autolink" community channel.

New contributors please see our Developer's Guide and our Plugins Guide.

https://github.com/mattermost/mattermost-plugin-autolink/pull/75 implemented most of the backend functionality to support this feature. Before it can be merged, we would like to add the capability to upload/save local files. It can be done with client-side commands, see https://github.com/mattermost/mattermost-plugin-jira/blob/6bb4e25bbef08a43b26716626382f518f3e28df1/webapp/src/hooks/hooks.js#L47 for an example.

See also #71 that introduced the config read/write capability.

adarj commented 5 years ago

Hello, I'm interested in contributing this feature. Just to confirm, the import and export commands should allow the user to upload/download config files from their local machine, correct?

levb commented 5 years ago

@adarj Welcome and thank you for taking this on!

RE: "allow the user to upload/download ... from local machine" - correct, but if that proves to be difficult to do directly, 0/5 an acceptable first implementation would be to export/import to mattermost files (uploaded as attachments for import, and for export, posted as a new message, with an attachment)

Also would be cool to have a "merge" capability in the import!

levb commented 5 years ago

@adarj I am going to re-label this as a "Up For Grabs" to have someone else add the requested "File Import/Export" UI feature. It seems like an essential addition we should have before merging the existing PR. They can be implemented with client-side /commands.

I will explicitly request that it is done as a continuation of your PR, since most of the backend code is already there and you should get the attribution for it.