• Home
  • Categories
  • Recent
  • Popular
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
v3.5.2 Latest
Buy Hosting

Why aren't people making plugins backwards-compatible?

Scheduled Pinned Locked Moved NodeBB Plugins
4 Posts 3 Posters 1.6k Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • PitaJP Offline
    PitaJP Offline
    PitaJ Global Moderator Plugin & Theme Dev
    wrote on last edited by
    #1

    Shouldn't we make new versions of plugins backwards compatible with at least 0.5.x?

    Why are people making separate versions for different NodeBB versions?

    1 Reply Last reply
    0
  • frissdiegurkeF Offline
    frissdiegurkeF Offline
    frissdiegurke Plugin & Theme Dev
    wrote on last edited by frissdiegurke
    #2

    NodeBB is still **0.**x, so it's not released yet. This is why I don't keep backward-compatibility.

    Because if you use software that isn't released yet you are a guy who doesn't care as much about stability as those who use released software only. Therefor you are one of those who stay on bleeding-edge of software. So there is no reason to keep backward-compatibility for those guys.

    And as long NodeBB upgrades don't break the old database-content you can update your NodeBB system without problems. If this wouldn't be the case I'd reconsider my thoughts about backwards-compatibility.

    Another point is that 0.6.0 breaks some plugins because of renaming of hooks, which would (didn't test it) cause plugins keeping backward-compatibility by containing the old hooks throwing deprecation-warnings on NodeBB-start 😉

    EDIT: but according to the "Plugin/Theme Dev" Group on this board I'm not a plugin-dev, so you can just ignore this ^^ So you now have to consider me as plugin-dev 😛 Thanks @julian

    julianJ PitaJP 2 Replies Last reply
    0
  • julianJ Offline
    julianJ Offline
    julian GNU/Linux
    replied to frissdiegurke on last edited by
    #3

    @frissdiegurke said:

    EDIT: but according to the "Plugin/Theme Dev" Group on this board I'm not a plugin-dev, so you can just ignore this ^^

    oh god 😓 rectified!

    1 Reply Last reply
    0
  • PitaJP Offline
    PitaJP Offline
    PitaJ Global Moderator Plugin & Theme Dev
    replied to frissdiegurke on last edited by
    #4

    @frissdiegurke yeah, but in simple things like a hook-refactor like in the case of the init hook, why are they still not just being backwards compatible? It seems easier.

    1 Reply Last reply
    0

Copyright © 2023 NodeBB | Contributors
  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Home
  • Categories
  • Recent
  • Popular
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development