-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Design formatter API to be more broad #318
Comments
okay, looking at this issue, i'm not sure of the long term suitability of the Basically, each provider would need a different set of parameters to the functions. nodebb and discourse have redirectors for postId, and both accept topicId/slug/postindex for topics, but something like phpbb would need topicId/page number/anchor for its urls... and something like a slack provider or an irc provider would have no concept of a url to a post. too much can change from provider to provider to give the I think the better approach there is to go with the approach already used in the provider for the objects. each has a @yamikuronue, your thoughts? See Post.url() for an example |
That's a great idea :) I think we should do a How about the other formatter methods? |
hmm.... i think the other ones are pretty agnostic. it might make sense to add support to them to have a "url-able" passed in instead of a string for urls for image/link/quote /etc. but to do so would be a breaking change. right now all the formatters are synchronous, and the url() function returns a i'll have to think on that one. but for now at least i think we're agreed on deprecate the |
yeah |
Is this done? |
i don't think there's been much traction on this one to be honest. it's something we need to look at and deal with "soon(tm)" but it's also one of those boring mainentance things so i've been dragging my paws on it, you know? :-) |
The URL function is everywhere already, so it's just a formatter change. I may tackle this soon then, I'm very familiar with formatter. |
The current formatter arguments are nodeBB specific, like URLForPost only taking a post ID (most forums require a thread ID as well).
The text was updated successfully, but these errors were encountered: